Microsoft Issues Mitigation for YellowKey BitLocker Bypass

Summary: Microsoft has released a mitigation for the BitLocker bypass vulnerability, named YellowKey and tracked as CVE-2026-45585. The flaw allows attackers to gain access to encrypted data by exploiting specially crafted 'FsTx' files in WinRE.

Microsoft Releases Mitigation for NTLM Relay Vulnerability Exploited in Active Attacks

Microsoft has released new mitigations and guidance for a high-risk NTLM relay vulnerability that security researchers say is already being exploited in real-world attacks. The flaw affects environments that still rely on the aging NTLM authentication protocol, once again exposing how legacy authentication mechanisms continue to create major security risks for enterprises worldwide.

The company warned that attackers can abuse the vulnerability to relay authentication requests and gain unauthorized access to systems, services, or sensitive network resources without needing to crack passwords directly. The issue is particularly dangerous in enterprise environments where NTLM remains enabled for compatibility reasons.

According to researchers, the attacks allow threat actors to intercept authentication traffic and forward it to another target service, effectively impersonating legitimate users. In some scenarios, attackers may achieve privilege escalation, lateral movement, or even domain compromise depending on the configuration of the affected environment.

Understanding NTLM Relay Attacks

NTLM (New Technology LAN Manager) is an older Microsoft authentication protocol that predates Kerberos. Although Microsoft has spent years encouraging organizations to transition away from NTLM, many enterprise systems still depend on it because of legacy applications, outdated devices, or compatibility requirements.

NTLM relay attacks exploit weaknesses in how authentication requests are handled across network services. Instead of stealing credentials outright, attackers capture authentication attempts and relay them to another server that trusts the authentication process.

This technique allows adversaries to:

  • Access internal services
  • Authenticate as legitimate users
  • Escalate privileges
  • Move laterally inside corporate networks
  • Deploy malware or ransomware
  • Extract sensitive information

Because the attack abuses legitimate authentication flows, detection can be difficult without advanced monitoring and logging.

Real-World Exploitation Already Observed

Security researchers tracking the vulnerability reported that attackers are actively exploiting the flaw in the wild. Threat actors are reportedly targeting organizations with improperly configured SMB, LDAP, HTTP, or other NTLM-enabled services.

Attack chains often begin with phishing, malicious file delivery, compromised endpoints, or coercion techniques that force systems to authenticate to attacker-controlled servers.

Researchers warned that modern NTLM relay attacks have evolved considerably in recent years. Attackers now combine relay techniques with:

  • IPv6 spoofing
  • Printer spooler abuse
  • WebDAV coercion
  • Rogue SMB servers
  • Active Directory misconfigurations
  • Credential theft frameworks

These methods can significantly increase the success rate of intrusions.

Microsoft’s Mitigation Guidance

Rather than issuing a traditional security patch alone, Microsoft released a set of mitigations and hardening recommendations designed to reduce exposure to NTLM relay attacks.

The company strongly encouraged organizations to:

  • Disable NTLM where possible
  • Enforce SMB signing
  • Require LDAP signing and channel binding
  • Enable Extended Protection for Authentication (EPA)
  • Restrict inbound NTLM traffic
  • Audit systems still using NTLM authentication
  • Migrate legacy applications to Kerberos or modern authentication methods

Microsoft emphasized that organizations should prioritize eliminating NTLM dependencies entirely whenever feasible.

The company has repeatedly warned that NTLM is increasingly becoming a liability in modern enterprise environments. Over the past several years, Microsoft has accelerated efforts to phase out legacy authentication technologies in favor of more secure alternatives.

Why Legacy Authentication Remains Dangerous

Despite years of warnings, NTLM continues to exist in many enterprise networks because:

  • Legacy applications still require it
  • Older devices lack modern authentication support
  • Complex environments delay migration projects
  • Organizations fear operational disruptions

This creates a significant attack surface for adversaries. Security experts have repeatedly linked NTLM relay attacks to ransomware intrusions, espionage operations, and large-scale enterprise breaches.

Attackers often prefer relay attacks because they avoid triggering traditional password-based security alerts. Since authentication occurs using legitimate credentials and trusted protocols, many defensive systems struggle to distinguish malicious activity from normal behavior.

Growing Focus on Identity-Based Attacks

The incident reflects a broader trend in cybersecurity: attackers increasingly target identity systems instead of relying solely on malware exploits. Modern threat actors understand that compromising authentication infrastructure can provide deeper and more persistent access than conventional malware infections.

Identity-focused attacks now commonly involve:

  • NTLM relay
  • Pass-the-hash attacks
  • Kerberos ticket abuse
  • OAuth token theft
  • Session hijacking
  • Active Directory compromise

Security teams are therefore being pushed toward zero-trust architectures that continuously verify identities and reduce reliance on legacy trust relationships.

Recommendations for Organizations

Security experts recommend organizations immediately review environments for NTLM exposure and prioritize mitigation efforts. Defensive measures include:

  • Conducting NTLM usage audits
  • Enforcing network segmentation
  • Monitoring anomalous authentication patterns
  • Disabling unnecessary services
  • Deploying multi-factor authentication
  • Reviewing Active Directory configurations
  • Updating legacy infrastructure

Organizations using outdated systems or unsupported applications may face elevated risk until migrations to modern authentication standards are completed.

The latest mitigation release from Microsoft underscores a growing reality for enterprise security teams: legacy authentication technologies remain one of the most attractive attack vectors for cybercriminals and advanced threat actors alike.

Key facts

  • CVE-2026-45585 is a BitLocker bypass vulnerability in Windows.
  • It allows attackers to gain full access by exploiting 'FsTx' files on USB drives or EFI partitions.
  • Mitigation steps include modifying system registry settings and configuring BitLocker with TPM+PIN.

Why it matters

The YellowKey vulnerability represents a significant risk for organizations that rely on BitLocker encryption, potentially allowing unauthorized access to sensitive data stored on devices with physical access.

X profile@thehackersnewshttps://twitter.com/thehackersnews
Embedded content for: Microsoft Issues Mitigation for YellowKey BitLocker Bypass