Improper authorization in Azure Red Hat OpenShift (ARO) allows an authorized attacker to elevate privileges over a network.
CVE-2026-56160
This critical-severity CVE scores 9.9 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 54% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.9
- EG Score
- 9.9(medium)
- EG Risk
- 45(Track)EG Risk 45/100SSVC: Track
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 computedSeverity99% × 45%Exploitation1% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 46%
- KEV
- Not listed
Published
July 23, 2026
Last Modified
September 9, 2026
Advisory Details (1)
Auto-updated Sep 9, 2026Security Update Guide - Microsoft Security Response Center
Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-56160Vendor Advisories for CVE-2026-56160(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 55× in last 7d / 287× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
Showing the most recent 100 of 613 total refreshes for this CVE.
- 2026-09-15 09:46 UTCEG score recompute
- 2026-09-15 09:46 UTCVendor advisory
- 2026-09-15 09:46 UTCGHSA enrichment
- 2026-09-15 03:11 UTCEPSS rescore
- 2026-09-14 16:11 UTCVendor advisory
- 2026-09-14 16:11 UTCGHSA enrichment
- 2026-09-14 09:27 UTCVendor advisory
- 2026-09-14 09:27 UTCGHSA enrichment
- 2026-09-14 05:45 UTCVendor advisory
- 2026-09-14 05:45 UTCGHSA enrichment
- 2026-09-14 02:04 UTCVendor advisory
- 2026-09-14 02:04 UTCGHSA enrichment
- 2026-09-13 22:22 UTCEG score recompute
- 2026-09-13 22:22 UTCVendor advisory
- 2026-09-13 22:22 UTCGHSA enrichment
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-13 15:28 UTCVendor advisory
- 2026-09-13 15:28 UTCGHSA enrichment
- 2026-09-13 11:16 UTCVendor advisory
- 2026-09-13 11:16 UTCGHSA enrichment
- 2026-09-13 07:34 UTCVendor advisory
- 2026-09-13 07:34 UTCGHSA enrichment
- 2026-09-13 03:53 UTCVendor advisory
- 2026-09-13 03:53 UTCGHSA enrichment
- 2026-09-13 00:11 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-13 00:11 UTCGHSA enrichment
- 2026-09-12 20:23 UTCVendor advisory
- 2026-09-12 20:23 UTCGHSA enrichment
- 2026-09-12 16:38 UTCEG score recompute
- 2026-09-12 16:38 UTCVendor advisory
- 2026-09-12 16:38 UTCGHSA enrichment
- 2026-09-12 12:56 UTCVendor advisory
- 2026-09-12 12:56 UTCGHSA enrichment
- 2026-09-12 09:14 UTCVendor advisory
- 2026-09-12 09:14 UTCGHSA enrichment
- 2026-09-12 05:07 UTCVendor advisory
- 2026-09-12 05:07 UTCGHSA enrichment
- 2026-09-12 00:49 UTCVendor advisory
- 2026-09-12 00:49 UTCGHSA enrichment
- 2026-09-11 20:27 UTCVendor advisory
- 2026-09-11 20:27 UTCGHSA enrichment
- 2026-09-11 16:40 UTCEG score recompute
- 2026-09-11 16:40 UTCVendor advisory
- 2026-09-11 16:40 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 07:13 UTCGHSA enrichment
- 2026-09-11 03:02 UTCGHSA enrichment
- 2026-09-10 20:55 UTCGHSA enrichment
- 2026-09-10 15:04 UTCEG score recompute
- 2026-09-10 15:03 UTCGHSA enrichment
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-09 21:06 UTCVendor advisory
- 2026-09-09 21:06 UTCGHSA enrichment
- 2026-09-09 08:53 UTCVendor advisory
- 2026-09-09 08:53 UTCGHSA enrichment
- 2026-09-08 22:41 UTCEG score recompute
- 2026-09-08 22:41 UTCVendor advisory
- 2026-09-08 22:41 UTCGHSA enrichment
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-08 21:04 UTCGHSA enrichment
- 2026-09-08 17:15 UTCVendor advisory
- 2026-09-08 17:14 UTCGHSA enrichment
- 2026-09-08 01:10 UTCVendor advisory
- 2026-09-08 01:10 UTCGHSA enrichment
- 2026-09-07 21:28 UTCEG score recompute
- 2026-09-07 21:28 UTCVendor advisory
- 2026-09-07 21:28 UTCGHSA enrichment
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 16:39 UTCEG score recompute
- 2026-09-06 16:39 UTCVendor advisory
- 2026-09-06 16:39 UTCGHSA enrichment
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 12:32 UTCVendor advisory
- 2026-09-06 12:32 UTCGHSA enrichment
- 2026-09-06 08:26 UTCVendor advisory
- 2026-09-06 08:26 UTCGHSA enrichment
- 2026-09-06 02:51 UTCVendor advisory
- 2026-09-06 02:51 UTCGHSA enrichment
- 2026-09-05 23:10 UTCVendor advisory
- 2026-09-05 23:09 UTCGHSA enrichment
- 2026-09-05 19:27 UTCEG score recompute
- 2026-09-05 19:27 UTCVendor advisory
- 2026-09-05 19:27 UTCGHSA enrichment
- 2026-09-05 06:56 UTCVendor advisory
- 2026-09-05 06:56 UTCGHSA enrichment
- 2026-09-04 22:35 UTCVendor advisory
- 2026-09-04 22:35 UTCGHSA enrichment
- 2026-09-04 17:05 UTCEG score recompute
- 2026-09-04 17:05 UTCVendor advisory
- 2026-09-04 17:05 UTCGHSA enrichment
- 2026-09-04 12:58 UTCEG score recompute
- 2026-09-04 12:58 UTCVendor advisory
- 2026-09-04 12:57 UTCGHSA enrichment
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-02 18:41 UTCEG score recompute
- 2026-09-02 18:41 UTCGHSA enrichment
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 23:20 UTCEG score recompute
- 2026-09-01 23:20 UTCVendor advisory
- 2026-09-01 23:20 UTCGHSA enrichment
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Same CWE
10 shownCWE-285
Frequently asked(5)
What is CVE-2026-56160?
When was CVE-2026-56160 disclosed?
Is CVE-2026-56160 actively exploited?
What is the CVSS score of CVE-2026-56160?
How do I remediate CVE-2026-56160?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-56160
Is Your Infrastructure Affected by CVE-2026-56160?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.