CVE-2026-56167

HIGHPre-NVD 8.58.5—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 5 sources updated this week
8.5EG
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.5Exploit: 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.5
EG Score
8.5(high)
EG Risk
43(Track)
EG Risk 43/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
Severity85% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
31%
KEV
Not listed

Published

July 23, 2026

Last Modified

July 26, 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 15× in last 7d / 15× 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-26 17:21 UTCEG score recompute
  2. 2026-07-26 17:21 UTCVendor advisory
  3. 2026-07-26 17:21 UTCGHSA enrichment
  4. 2026-07-26 15:27 UTCEG score recompute
  5. 2026-07-26 15:27 UTCVendor advisory
  6. 2026-07-26 15:26 UTCGHSA enrichment
  7. 2026-07-26 14:54 UTCEPSS rescore
  8. 2026-07-26 03:06 UTCEG score recompute
  9. 2026-07-26 03:06 UTCVendor advisory
  10. 2026-07-26 03:06 UTCGHSA enrichment
  11. 2026-07-25 14:18 UTCEPSS rescore
  12. 2026-07-24 14:18 UTCEPSS rescore
  13. 2026-07-24 00:18 UTCEG score recompute
  14. 2026-07-24 00:18 UTCVendor advisory
  15. 2026-07-24 00:17 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

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 26, 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.2% of all scored CVEs.
What is the CVSS score of CVE-2026-56167?
CVE-2026-56167 has a CVSS v4.0 base score of 8.5 (CNA self-assessment; NVD's own analysis pending).
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