Insufficient granularity of access control in Active Directory Federation Services (AD FS) allows an authorized attacker to elevate privileges locally.
CVE-2026-56155
“▲” beside the score: it is higher than the CVSS score beside it.
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2026-07-14), indicating real-world exploitation has been confirmed by US federal agencies. The CNA's CVSS baseline 7.8 retained for reference (NVD's own analysis pending). Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
A fix is available — apply it.
- CVSS v3
- 7.8
- EG Score
- 9.0CRITICALhigh confidence
- EG Risk
- 81EG Risk 81/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity90% × 45%The EG Score, 9.0 of 10.Exploitation100% × 40%Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact. - EPSS PROB
- 0.3%
- EPSS %ILE
- 26th
- KEV
- ⚠ Exploited
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Attend at medium and Act at high mission impact.
A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.
In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
CISA required action“Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.”
Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2026-56155 · https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk · https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk · https://nvd.nist.gov/vuln/detail/CVE-2026-56155 · https://learn.microsoft.com/en-us/windows-server/identity/ad-fs/decommission/adfs-decommission-guide
Published
July 14, 2026
Last Modified
October 8, 2026
Advisory Details (2)
Auto-updated Oct 12, 2026Security Update Guide - Microsoft Security Response Center
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-56155Known Exploited Vulnerabilities Catalog | CISA
Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-56155Vendor Advisories for CVE-2026-56155(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 84× in last 7d / 439× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 100 of 6,295 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 6,195 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-14 03:07 UTCEG score recompute
- 2026-10-14 03:06 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-10-13 04:49 UTCEG score recompute
- 2026-10-13 04:49 UTCVendor advisory
- 2026-10-13 04:49 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-10-12 15:55 UTCEG score recompute
- 2026-10-12 06:29 UTCVendor advisory
- 2026-10-12 06:29 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-12 02:49 UTCVendor advisory
- 2026-10-12 02:49 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-11 23:09 UTCVendor advisory
- 2026-10-11 23:09 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-11 19:30 UTCEG score recompute
- 2026-10-11 19:30 UTCVendor advisory
- 2026-10-11 19:30 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-11 16:53 UTCEG score recompute
- 2026-10-11 15:50 UTCVendor advisory
- 2026-10-11 15:50 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-11 14:16 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-10-11 12:11 UTCEG score recompute
- 2026-10-11 12:11 UTCVendor advisory
- 2026-10-11 12:11 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
Show 75 moreShow fewer
- 2026-10-11 08:31 UTCVendor advisory
- 2026-10-11 08:31 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-11 04:51 UTCVendor advisory
- 2026-10-11 04:51 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-11 01:11 UTCVendor advisory
- 2026-10-11 01:10 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-10 21:30 UTCEG score recompute
- 2026-10-10 21:30 UTCVendor advisory
- 2026-10-10 21:29 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-10-10 17:48 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-10 14:09 UTCVendor advisory
- 2026-10-10 14:09 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-10 10:29 UTCVendor advisory
- 2026-10-10 10:29 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-10 06:50 UTCVendor advisory
- 2026-10-10 06:50 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-10 03:10 UTCVendor advisory
- 2026-10-10 03:10 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-09 23:31 UTCEG score recompute
- 2026-10-09 23:31 UTCVendor advisory
- 2026-10-09 23:31 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-10-09 19:52 UTCVendor advisory
- 2026-10-09 19:52 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-09 16:12 UTCVendor advisory
- 2026-10-09 16:12 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-09 12:33 UTCVendor advisory
- 2026-10-09 12:33 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-09 08:53 UTCVendor advisory
- 2026-10-09 08:53 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-09 05:13 UTCVendor advisory
- 2026-10-09 05:13 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-09 01:33 UTCVendor advisory
- 2026-10-09 01:33 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-08 21:54 UTCVendor advisory
- 2026-10-08 21:54 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-08 18:15 UTCVendor advisory
- 2026-10-08 18:14 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-08 17:49 UTCEG score recompute
- 2026-10-08 17:49 UTCVendor advisory
- 2026-10-08 17:49 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-10-08 14:10 UTCVendor advisory
- 2026-10-08 14:09 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-08 10:29 UTCVendor advisory
- 2026-10-08 10:29 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-08 06:50 UTCVendor advisory
- 2026-10-08 06:50 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-08 03:10 UTCEG score recompute
- 2026-10-08 03:10 UTCVendor advisory
- 2026-10-08 03:10 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-10-07 23:30 UTCVendor advisory
- 2026-10-07 23:30 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-07 19:51 UTCVendor advisory
- 2026-10-07 19:51 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-07 16:12 UTCVendor advisory
- 2026-10-07 16:11 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-07 12:32 UTCVendor advisory
- 2026-10-07 12:32 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-07 08:51 UTCVendor advisory
- 2026-10-07 08:51 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-07 05:12 UTCVendor advisory
- 2026-10-07 05:12 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-07 01:32 UTCVendor advisory
- 2026-10-07 01:32 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-06 21:52 UTCVendor advisory
- 2026-10-06 21:52 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-06 18:13 UTCEG score recompute
- 2026-10-06 18:13 UTCVendor advisory
- 2026-10-06 18:13 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-10-06 14:34 UTCVendor advisory
- 2026-10-06 14:34 UTCGHSA enrichmentGHSA-p436-qch3-9m59 · GitHub severity HIGH · GitHub CVSS 7.8
Related CVEs(same CWE)
Frequently asked(6)
What is CVE-2026-56155?
When was CVE-2026-56155 made public?
Is CVE-2026-56155 actively exploited?
What is the CVSS score of CVE-2026-56155?
Which products are affected by CVE-2026-56155?
How do I remediate CVE-2026-56155?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-56155
Is Your Infrastructure Affected by CVE-2026-56155?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.