09.07.2025

Critical vulnerability in Windows authentication

We would like to draw your attention to a critical security vulnerability in Microsoft Windows that currently poses an acute risk to your IT infrastructure. The vulnerability with a CVSS score of 9.8 affects almost all current Windows and Windows Server versions – including Windows Server 2008 R2 – and allows attackers to execute malicious code with system privileges without user interaction.

Immediate patching of affected systems is urgently needed.

IT security researchers report active attacks in which, among other things, existing web sessions were compromised and authentications were obtained without the knowledge of the users – suggesting that active multi-factor authentication could also be bypassed.

What happened?

Microsoft has identified and published a serious vulnerability (CVE-2025-47981) in the SPNEGO NEGOEX authentication protocol – an important part of Windows authentication in the domain environment, among other things. This vulnerability allows attackers to execute arbitrary code with system privileges – without logging in and without any user action.

The threat is particularly serious because Microsoft classifies it as “wormable”. This means that the malware can spread automatically via networks. According to Microsoft, a first abuse of this vulnerability is expected shortly.

Reported vulnerability

The vulnerability allows unauthenticated attackers to execute code with system privileges through crafted NETWORK messages, triggering a “heap-based buffer overflow”. This is a bug in the handling of memory. When they are executed, programs reserve space in the so-called heap – a dynamic memory area that is flexibly requested at runtime.

If more is written in this area than is intended, neighboring memory areas can be manipulated. This allows attackers to inject and execute their own malicious code – in this case, even with the highest privileges.

What is affected?

This vulnerability affects all Windows clients starting with Windows 10 version 1607 because these versions have the following Group Policy enabled by default: “Network Security: Allow PKU2U authentication requeststo this computer with online identities”.

This default setting means that the attack surface is already active on many systems – even without any special configuration.

Systems in which NEGOEX is used in combination with the following services are also particularly at risk:

  • Active Directory / Domain Controller
  • RDP Accesses
  • VPN Gateways
  • SMB File Shares
  • Windows Remote Management (WinRM)

What can I do?

The CVE-2025-47981 vulnerability poses an acute threat to Windows-based networks. The combination of high criticality, ease of exploitation, and the possibility of automatic distribution makes this vulnerability particularly dangerous.

We recommend that you act immediately to prevent potential harm:

  1. Priority: Install the latest Microsoft security updates immediately, especially on publicly accessible or business-critical systems.
  2. If you are unable to patch, block network access to ports 135, 445, and 5985 if technically possible.
  3. Use Group Policy (GPO) to disable the “Allow PKU2U authentication requests” setting if not needed.
  4. Check which systems are potentially vulnerable and prioritize securing sensitive services such as AD, RDP, or VPN.

From experts for experts:

Important note: Please note that blocking ports 135, 445 and 5985 may result in the following effects:

  • File shares (network drives): These may no longer be accessible.
  • Group Policy: GPOs can fail or be delayed depending on the environment.
  • Remote PowerShell (WinRM): Script-based solutions such as SCCM, Ansible, or other automation tools may no longer work.
  • MI/DCOM access: Tools for monitoring, inventory, or administration can be disrupted, e.g. when connecting to remote systems.

Here’s how you can identify a potential exploitation of the vulnerability:

  • Use EDR/antivirus with memory analysis (e.g. Defender for Endpoint, CrowdStrike, SentinelOne) to detect suspicious activity in memory.
  • Enable event log monitoring – pay special attention to LSASS crashes and unusual network connections.
  • Use Sysmon (especially the events: ID 1: Process start, ID 10: Access to other processes, ID 11: File operations)