CVE-2026-56155: AD FS local privilege escalation

Quick Answer

CISA added CVE-2026-56155 to its Known Exploited Vulnerabilities catalog on 2026-07-14, confirming that exploitation has occurred. If you operate Microsoft Active Directory Federation Services, identify the exact version and relevant configuration now, preserve security evidence, and follow the live vendor remediation. A KEV match does not prove your system was compromised, and installing an update does not rule out earlier exploitation.

Last verified: 2026-09-17 UTC. CISA KEV snapshot version 2026.09.16. Recheck the live advisory before changing production.

Context

Status At A Glance

Product scope	Microsoft — Active Directory Federation Services
CVE	CVE-2026-56155
TechGeeks response tier	P0 — confirm an exact match and act now
CISA KEV added	2026-07-14
Vendor severity	Important
CVSS	7.8 (CVSS v3.1 base)
Ransomware field	Unknown — this is not the same as No; CISA has not marked the field Known.
Forensic-triage field	No in the current CISA field; organizations should still investigate when exposure or evidence warrants it.
CWE	CWE-1220
Federal remediation date	2026-07-28 — applies to covered federal agencies; other organizations should set a risk-based deadline.

What Happened

Microsoft Active Directory Federation Services Insufficient Granularity of Access Control Vulnerability . Microsoft Active Directory Federation Services contains an insufficient granularity of access control vulnerability that allows an authorized attacker to elevate privileges locally. CISA's KEV listing confirms exploitation evidence, but it does not state how widespread the activity is or prove that any particular installation was compromised.

Affected Scope

Active Directory Federation Services installations on Windows Server releases listed by Microsoft; validate the exact server build and AD FS role in the live advisory.

Match the exact edition, hardware or virtual platform, release, patch level, enabled feature, and management exposure. A product-family name alone is not enough to establish applicability.

Steps

What To Do Now

1. Confirm. Inventory every Active Directory Federation Services asset and record its exact version, patch level, role, relevant configuration, and exposure.
2. Preserve. Save UTC timestamps, off-device authentication, firewall, proxy, DNS, endpoint, application, and SIEM evidence before logs rotate or a disruptive change removes context.
3. Contain. Restrict unnecessary internet and management-plane access using supported controls. Follow the live advisory: Open the live Microsoft advisory.
4. Remediate. Install the applicable Windows Server cumulative update on AD FS servers and confirm that each node is on a fixed build.
5. Validate. Verify the resulting version or patch level, service health, logging, expected access, an expected denial, and representative dependent workflows.
6. Escalate. If exposure overlapped the vulnerable period or evidence is suspicious, treat the system as a potential incident and follow vendor and incident-response recovery guidance.

Fixed Releases And Mitigation

Verified fixed release, patch level, or update guidance captured at the last check:

A fixed build or KB was not safely preserved in the research record. Check the live vendor advisory before production changes; do not infer a fixed version from this summary.

Mitigation boundary: No specific Microsoft workaround is safely captured in the current research notes. Restrict local administrative access and follow Microsoft's supported AD FS lifecycle guidance while patching.

A workaround, access restriction, or provider-side control reduces a described path; it does not necessarily remove vulnerable code or erase compromise.

Investigation And Recovery

The flaw allows a local low-privilege user to gain administrator rights. CISA lists it as known exploited; inspect AD FS hosts for anomalous local logons, privilege changes, and post-escalation activity.

When an attacker may have gained administrative, root, SYSTEM, identity, management-plane, or code-execution access, patching alone is not an eradication claim. Preserve evidence, scope affected accounts and downstream systems, rotate exposed credentials or certificates when justified, and rebuild from a trusted source when vendor or incident-response guidance requires it.

Notes

Exploitation Evidence

Vendor statement: Microsoft marked Exploited: Yes at original publication.

CISA statement: CVE-2026-56155 was added to KEV on 2026-07-14. The ransomware field is Unknown, and the forensic-triage field is No. These are separate signals.

Validation And Boundaries

This notice does not prove that every product carrying the family name is affected, that exploitation is widespread, that a clean indicator search rules out compromise, or that a successful update restored trust. TechGeeks has not reproduced the exploit and does not replace the vendor advisory, asset inventory, vulnerability scanner, or incident-response process.

Related TechGeeks Resources

• Security Hot Page
• All Security Notices
• What to Do When a Device Hits CISA KEV
• Router CVE Exposure, Version, and Mitigation Checklist
• IoT Firmware Update and End-of-Support Checklist
• Live Protect and Runtime Vulnerability Shielding

References

• Microsoft security advisory
• Microsoft security advisory
• CISA guidance
• CISA guidance
• NVD CVE record
• Microsoft security advisory
• CISA source

Wrap-Up

Record whether CVE-2026-56155 applies to your environment. If it does, assign an owner, preserve the change and investigation evidence, complete the vendor action, and document the validated result.

Correction policy: If a primary source changes affected versions, remediation, exploitation status, or recovery guidance, TechGeeks will update this page and its verification date.