CVE-2026-56163

CRITICALPre-NVD 10.010.0—
EchelonGraph scoreHIGH confidence

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-24. the CNA's CVSS baseline 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 5 sources updated this week
10.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 10.0Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Missing authentication for critical function in Microsoft Azure Kubernetes Service allows an unauthorized attacker to elevate privileges over a network.

CVSS v3
10.0
EG Score
10.0(high)
EG Risk
60(Track)
EG Risk 60/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 computed
Severity100% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
57%
KEV
Not listed

Published

July 24, 2026

Last Modified

July 27, 2026

Advisory Details (1)

Auto-updated Jul 28, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

Security 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-56163

Vendor Advisories for CVE-2026-56163(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 40× in last 7d / 40× 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.

  1. 2026-07-28 08:01 UTCVendor advisory
  2. 2026-07-28 08:01 UTCGHSA enrichment
  3. 2026-07-28 03:57 UTCVendor advisory
  4. 2026-07-28 03:57 UTCGHSA enrichment
  5. 2026-07-27 23:57 UTCVendor advisory
  6. 2026-07-27 23:57 UTCGHSA enrichment
  7. 2026-07-27 22:16 UTCVendor advisory
  8. 2026-07-27 22:16 UTCGHSA enrichment
  9. 2026-07-27 21:50 UTCVendor advisory
  10. 2026-07-27 21:50 UTCGHSA enrichment
  11. 2026-07-27 20:22 UTCVendor advisory
  12. 2026-07-27 20:22 UTCGHSA enrichment
  13. 2026-07-27 16:17 UTCEG score recompute
  14. 2026-07-27 16:17 UTCVendor advisory
  15. 2026-07-27 16:17 UTCGHSA enrichment
  16. 2026-07-27 13:31 UTCVendor advisory
  17. 2026-07-27 13:31 UTCGHSA enrichment
  18. 2026-07-27 09:30 UTCVendor advisory
  19. 2026-07-27 09:30 UTCGHSA enrichment
  20. 2026-07-27 05:29 UTCVendor advisory
  21. 2026-07-27 05:28 UTCGHSA enrichment
  22. 2026-07-27 01:26 UTCVendor advisory
  23. 2026-07-27 01:26 UTCGHSA enrichment
  24. 2026-07-26 21:23 UTCVendor advisory
  25. 2026-07-26 21:23 UTCGHSA enrichment
Show 15 more
  1. 2026-07-26 17:21 UTCEG score recompute
  2. 2026-07-26 17:21 UTCVendor advisory
  3. 2026-07-26 17:20 UTCGHSA enrichment
  4. 2026-07-26 13:45 UTCEG score recompute
  5. 2026-07-26 13:45 UTCVendor advisory
  6. 2026-07-26 13:45 UTCGHSA enrichment
  7. 2026-07-26 09:43 UTCVendor advisory
  8. 2026-07-26 09:43 UTCGHSA enrichment
  9. 2026-07-26 03:00 UTCEG score recompute
  10. 2026-07-26 03:00 UTCVendor advisory
  11. 2026-07-26 03:00 UTCGHSA enrichment
  12. 2026-07-25 14:18 UTCEPSS rescore
  13. 2026-07-24 15:13 UTCEG score recompute
  14. 2026-07-24 15:13 UTCVendor advisory
  15. 2026-07-24 15:13 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-56163?
CVE-2026-56163 is a critical vulnerability published on July 24, 2026. Missing authentication for critical function in Microsoft Azure Kubernetes Service allows an unauthorized attacker to elevate privileges over a network.
When was CVE-2026-56163 disclosed?
CVE-2026-56163 was first published in the National Vulnerability Database on July 24, 2026, with the most recent update on July 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56163 actively exploited?
CVE-2026-56163 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 43.4% of all scored CVEs.
What is the CVSS score of CVE-2026-56163?
CVE-2026-56163 has a CVSS v4.0 base score of 10.0 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-56163?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56163, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-56163

Explore →

Is Your Infrastructure Affected by CVE-2026-56163?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs