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 65% 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 — 4 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
35%
KEV
Not listed

Published

July 23, 2026

Last Modified

September 9, 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 29× in last 7d / 143× 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 299 total refreshes for this CVE.

  1. 2026-09-15 09:46 UTCEG score recompute
  2. 2026-09-15 09:46 UTCVendor advisory
  3. 2026-09-15 09:46 UTCGHSA enrichment
  4. 2026-09-15 03:11 UTCEPSS rescore
  5. 2026-09-14 06:56 UTCVendor advisory
  6. 2026-09-14 06:56 UTCGHSA enrichment
  7. 2026-09-13 18:36 UTCEG score recompute
  8. 2026-09-13 18:36 UTCVendor advisory
  9. 2026-09-13 18:36 UTCGHSA enrichment
  10. 2026-09-13 16:47 UTCEPSS rescore
  11. 2026-09-13 06:14 UTCVendor advisory
  12. 2026-09-13 06:14 UTCGHSA enrichment
  13. 2026-09-12 17:42 UTCEG score recompute
  14. 2026-09-12 17:42 UTCVendor advisory
  15. 2026-09-12 17:42 UTCGHSA enrichment
  16. 2026-09-12 05:07 UTCVendor advisory
  17. 2026-09-12 05:07 UTCGHSA enrichment
  18. 2026-09-11 16:40 UTCEG score recompute
  19. 2026-09-11 16:40 UTCVendor advisory
  20. 2026-09-11 16:40 UTCGHSA enrichment
  21. 2026-09-11 14:53 UTCEPSS rescore
  22. 2026-09-11 03:25 UTCGHSA enrichment
  23. 2026-09-10 15:04 UTCEG score recompute
  24. 2026-09-10 15:04 UTCGHSA enrichment
  25. 2026-09-10 09:35 UTCEPSS rescore
Show 75 more
  1. 2026-09-09 21:06 UTCVendor advisory
  2. 2026-09-09 21:06 UTCGHSA enrichment
  3. 2026-09-09 11:01 UTCVendor advisory
  4. 2026-09-09 11:01 UTCGHSA enrichment
  5. 2026-09-08 22:41 UTCEG score recompute
  6. 2026-09-08 22:41 UTCVendor advisory
  7. 2026-09-08 22:41 UTCGHSA enrichment
  8. 2026-09-08 22:01 UTCEPSS rescore
  9. 2026-09-08 21:04 UTCGHSA enrichment
  10. 2026-09-08 17:16 UTCVendor advisory
  11. 2026-09-08 17:15 UTCGHSA enrichment
  12. 2026-09-07 21:28 UTCEG score recompute
  13. 2026-09-07 21:28 UTCVendor advisory
  14. 2026-09-07 21:28 UTCGHSA enrichment
  15. 2026-09-07 16:01 UTCEPSS rescore
  16. 2026-09-06 13:47 UTCEPSS rescore
  17. 2026-09-06 08:26 UTCVendor advisory
  18. 2026-09-06 08:26 UTCGHSA enrichment
  19. 2026-09-05 19:27 UTCEG score recompute
  20. 2026-09-05 19:27 UTCVendor advisory
  21. 2026-09-05 19:27 UTCGHSA enrichment
  22. 2026-09-04 22:36 UTCEG score recompute
  23. 2026-09-04 22:36 UTCVendor advisory
  24. 2026-09-04 22:35 UTCGHSA enrichment
  25. 2026-09-04 12:58 UTCEG score recompute
  26. 2026-09-04 12:58 UTCVendor advisory
  27. 2026-09-04 12:57 UTCGHSA enrichment
  28. 2026-09-04 05:07 UTCEPSS rescore
  29. 2026-09-02 18:41 UTCEG score recompute
  30. 2026-09-02 18:41 UTCGHSA enrichment
  31. 2026-09-02 14:12 UTCEPSS rescore
  32. 2026-09-01 23:20 UTCEG score recompute
  33. 2026-09-01 23:20 UTCVendor advisory
  34. 2026-09-01 23:20 UTCGHSA enrichment
  35. 2026-09-01 13:54 UTCEPSS rescore
  36. 2026-09-01 04:40 UTCEPSS rescore
  37. 2026-08-31 15:39 UTCVendor advisory
  38. 2026-08-31 15:39 UTCGHSA enrichment
  39. 2026-08-31 01:14 UTCEG score recompute
  40. 2026-08-31 01:14 UTCVendor advisory
  41. 2026-08-31 01:14 UTCGHSA enrichment
  42. 2026-08-30 19:17 UTCEPSS rescore
  43. 2026-08-30 12:54 UTCEG score recompute
  44. 2026-08-30 12:54 UTCVendor advisory
  45. 2026-08-30 12:54 UTCGHSA enrichment
  46. 2026-08-30 01:22 UTCEPSS rescore
  47. 2026-08-30 00:27 UTCEG score recompute
  48. 2026-08-30 00:27 UTCVendor advisory
  49. 2026-08-30 00:27 UTCGHSA enrichment
  50. 2026-08-28 21:41 UTCEPSS rescore
  51. 2026-08-28 21:10 UTCVendor advisory
  52. 2026-08-28 21:10 UTCGHSA enrichment
  53. 2026-08-27 23:45 UTCEG score recompute
  54. 2026-08-27 23:45 UTCVendor advisory
  55. 2026-08-27 23:45 UTCGHSA enrichment
  56. 2026-08-27 14:25 UTCEPSS rescore
  57. 2026-08-27 11:22 UTCVendor advisory
  58. 2026-08-27 11:22 UTCGHSA enrichment
  59. 2026-08-26 23:02 UTCEG score recompute
  60. 2026-08-26 23:02 UTCVendor advisory
  61. 2026-08-26 23:02 UTCGHSA enrichment
  62. 2026-08-26 14:46 UTCEPSS rescore
  63. 2026-08-26 10:40 UTCVendor advisory
  64. 2026-08-26 10:40 UTCGHSA enrichment
  65. 2026-08-25 22:17 UTCEG score recompute
  66. 2026-08-25 22:17 UTCVendor advisory
  67. 2026-08-25 22:17 UTCGHSA enrichment
  68. 2026-08-25 13:49 UTCEPSS rescore
  69. 2026-08-25 09:28 UTCVendor advisory
  70. 2026-08-25 09:28 UTCGHSA enrichment
  71. 2026-08-24 21:08 UTCVendor advisory
  72. 2026-08-24 21:08 UTCGHSA enrichment
  73. 2026-08-24 19:53 UTCEG score recompute
  74. 2026-08-24 19:53 UTCVendor advisory
  75. 2026-08-24 19:53 UTCGHSA enrichment

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 September 9, 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 65.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