CVE-2025-26685Public exploit

DSA credential disclosure via coerced NTLM authentication

Published May 13, 2025 · Updated Feb 13, 2026

Improper authentication in Microsoft Defender for Identity allows remote attackers to capture a DSA account's Net-NTLM hash. The classic sensor's lateral-movement-path collector reacts to a crafted domain-controller event by querying the attacker's host over SAM-R, permitting Kerberos to fall back to NTLM and sending DSA authentication material. Exploitation requires local-network access, a DNS record for the attacker host, and an anonymous connection that generates the trigger event; cracking or relaying the captured hash can compromise the DSA account only when additional conditions permit it.

CVSS severity6.5
Medium
EPSS probability0.70%
Next 30 days · Sep 17, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper authentication in Microsoft Defender for Identity allows remote attackers to capture a DSA account's Net-NTLM hash. The classic sensor's lateral-movement-path collector reacts to a crafted domain-controller event by querying the attacker's host over SAM-R, permitting Kerberos to fall back to NTLM and sending DSA authentication material. Exploitation requires local-network access, a DNS record for the attacker host, and an anonymous connection that generates the trigger event; cracking or relaying the captured hash can compromise the DSA account only when additional conditions permit it.

The record

CVE
CVE-2025-26685
Published
May 13, 2025
Updated
Feb 13, 2026
Vendor
Microsoft
Product
Microsoft Defender for Identity
Classifications
CWE-287, T1187
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. May 13, 2025CVE publishedPublication date reported by the CVE source.
  2. Feb 13, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=-

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesunauthenticated

What is affected?

Microsoft · Microsoft Defender for Identityversion=-

Published CVSS scores

6.5Microsoft CorporationCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-287Improper Authentication
T1187Forced Authentication

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo