CVE-2026-56167

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 69% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 6 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

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

Server-side request forgery (ssrf) in Azure AI Search allows an authorized attacker to elevate privileges over a network.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
31%
KEV
Not listed

Published

July 23, 2026

Last Modified

July 29, 2026

Advisory Details (1)

Auto-updated Jul 24, 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-56167

Vendor Advisories for CVE-2026-56167(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 52× in last 7d / 52× 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-30 03:00 UTCEG score recompute
  2. 2026-07-30 03:00 UTCVendor advisory
  3. 2026-07-30 03:00 UTCGHSA enrichment
  4. 2026-07-30 01:30 UTCEPSS rescore
  5. 2026-07-30 01:30 UTCEPSS rescore
  6. 2026-07-29 14:39 UTCEG score recompute▲ 0.30
  7. 2026-07-29 14:39 UTCVendor advisory
  8. 2026-07-29 14:39 UTCGHSA enrichment
  9. 2026-07-29 14:39 UTCNVD updateCVSS v3 → 8.8
  10. 2026-07-29 09:52 UTCVendor advisory
  11. 2026-07-29 09:52 UTCGHSA enrichment
  12. 2026-07-28 21:31 UTCVendor advisory
  13. 2026-07-28 21:31 UTCGHSA enrichment
  14. 2026-07-28 15:38 UTCEG score recompute
  15. 2026-07-28 15:38 UTCVendor advisory
  16. 2026-07-28 15:38 UTCGHSA enrichment
  17. 2026-07-28 15:37 UTCEPSS rescore
  18. 2026-07-28 12:19 UTCVendor advisory
  19. 2026-07-28 12:19 UTCGHSA enrichment
  20. 2026-07-27 23:58 UTCVendor advisory
  21. 2026-07-27 23:57 UTCGHSA enrichment
  22. 2026-07-27 22:16 UTCVendor advisory
  23. 2026-07-27 22:16 UTCGHSA enrichment
  24. 2026-07-27 21:51 UTCEG score recompute
  25. 2026-07-27 21:51 UTCVendor advisory
Show 27 more
  1. 2026-07-27 21:50 UTCGHSA enrichment
  2. 2026-07-27 21:39 UTCEG score recompute
  3. 2026-07-27 21:39 UTCVendor advisory
  4. 2026-07-27 21:38 UTCGHSA enrichment
  5. 2026-07-27 20:55 UTCEG score recompute
  6. 2026-07-27 20:55 UTCVendor advisory
  7. 2026-07-27 20:55 UTCGHSA enrichment
  8. 2026-07-27 16:17 UTCEG score recompute
  9. 2026-07-27 16:17 UTCVendor advisory
  10. 2026-07-27 16:17 UTCGHSA enrichment
  11. 2026-07-27 05:41 UTCVendor advisory
  12. 2026-07-27 05:41 UTCGHSA enrichment
  13. 2026-07-26 17:21 UTCEG score recompute
  14. 2026-07-26 17:21 UTCVendor advisory
  15. 2026-07-26 17:21 UTCGHSA enrichment
  16. 2026-07-26 15:27 UTCEG score recompute
  17. 2026-07-26 15:27 UTCVendor advisory
  18. 2026-07-26 15:26 UTCGHSA enrichment
  19. 2026-07-26 14:54 UTCEPSS rescore
  20. 2026-07-26 03:06 UTCEG score recompute
  21. 2026-07-26 03:06 UTCVendor advisory
  22. 2026-07-26 03:06 UTCGHSA enrichment
  23. 2026-07-25 14:18 UTCEPSS rescore
  24. 2026-07-24 14:18 UTCEPSS rescore
  25. 2026-07-24 00:18 UTCEG score recompute
  26. 2026-07-24 00:18 UTCVendor advisory
  27. 2026-07-24 00:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-56167?
CVE-2026-56167 is a high vulnerability published on July 23, 2026. Server-side request forgery (ssrf) in Azure AI Search allows an authorized attacker to elevate privileges over a network.
When was CVE-2026-56167 disclosed?
CVE-2026-56167 was first published in the National Vulnerability Database on July 23, 2026, with the most recent update on July 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56167 actively exploited?
CVE-2026-56167 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 69.1% of all scored CVEs.
What is the CVSS score of CVE-2026-56167?
CVE-2026-56167 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-56167?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56167, 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-56167

Explore →

Is Your Infrastructure Affected by CVE-2026-56167?

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

Start Free Scan →Browse All CVEs