CVE-2026-56155Known exploitation

Local privilege escalation via permissive DKM ACL

Published Jul 14, 2026 · Updated Jul 14, 2026

Access-control weakness in Microsoft AD FS on affected Windows releases allows local authenticated users to elevate privileges. The AD FS DKM container accepts overly permissive ACLs, exposing symmetric key material that protects token-signing private keys. Read access to that material lets attackers decrypt the signing keys and compromise federation trust.

CVSS severity7.8
High
EPSS probability0.35%
Next 30 days · Sep 16, 2026
Known exploitationReported
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

Access-control weakness in Microsoft AD FS on affected Windows releases allows local authenticated users to elevate privileges. The AD FS DKM container accepts overly permissive ACLs, exposing symmetric key material that protects token-signing private keys. Read access to that material lets attackers decrypt the signing keys and compromise federation trust.

The record

CVE
CVE-2026-56155
Published
Jul 14, 2026
Updated
Jul 14, 2026
Vendor
Microsoft
Product
Windows Server 2019
Classifications
CWE-1220, T1552.004
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Jul 14, 2026CVE publishedPublication date reported by the CVE source.
  2. Jul 14, 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=10.0.17763.0 <10.0.17763.9020

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Microsoft · Windows Server 2019version=10.0.17763.0 <10.0.17763.9020
Microsoft · Windows Server 2025 (Server Core installation)version=10.0.26100.0 <10.0.26100.33158
Microsoft · Windows Server 2016 (Server Core installation)version=10.0.14393.0 <10.0.14393.9339
Microsoft · Windows Server 2012 (Server Core installation)version=6.2.9200.0 <6.2.9200.26226
Microsoft · Windows Server 2012version=6.2.9200.0 <6.2.9200.26226
Microsoft · Windows Server 2016version=10.0.14393.0 <10.0.14393.9339
Microsoft · Windows Server 2012 R2 (Server Core installation)version=6.3.9600.0 <6.3.9600.23291
Microsoft · Windows Server 2019 (Server Core installation)version=10.0.17763.0 <10.0.17763.9020
Microsoft · Windows 10 Version 1607version=10.0.14393.0 <10.0.14393.9339
Microsoft · Windows Server 2022version=10.0.20348.0 <10.0.20348.5386
Microsoft · Windows Server 2025version=10.0.26100.0 <10.0.26100.33158
Microsoft · Windows 10 Version 1809version=10.0.17763.0 <10.0.17763.9020
Microsoft · Windows Server 2012 R2version=6.3.9600.0 <6.3.9600.23291

Published CVSS scores

7.8MicrosoftCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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)
Vectorlocal
Privilegesauthenticated
Known exploitationReported
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-1220Insufficient Granularity of Access Control
T1552.004Unsecured Credentials: Private Keys

Public exploit references

No public exploit references are available in this record.

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

Reported exploitation

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