CVE-2026-85917

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-18. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.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 Foundry allows an unauthorized attacker to elevate privileges over a network.

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

Published

September 17, 2026

Last Modified

September 19, 2026

Advisory Details (1)

Auto-updated Sep 17, 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-85917

Vendor Advisories for CVE-2026-85917(1)

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.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 37× in last 7d / 37× 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-09-21 09:05 UTCEG score recompute
  2. 2026-09-21 09:05 UTCVendor advisory
  3. 2026-09-21 09:05 UTCGHSA enrichment
  4. 2026-09-20 20:16 UTCEPSS rescore
  5. 2026-09-20 19:58 UTCVendor advisory
  6. 2026-09-20 19:58 UTCGHSA enrichment
  7. 2026-09-20 06:51 UTCVendor advisory
  8. 2026-09-20 06:50 UTCGHSA enrichment
  9. 2026-09-19 17:38 UTCEG score recompute
  10. 2026-09-19 17:38 UTCVendor advisory
  11. 2026-09-19 17:38 UTCGHSA enrichment
  12. 2026-09-19 04:31 UTCEG score recompute
  13. 2026-09-19 04:31 UTCVendor advisory
  14. 2026-09-19 04:31 UTCGHSA enrichment
  15. 2026-09-19 04:01 UTCVendor advisory
  16. 2026-09-19 04:01 UTCGHSA enrichment
  17. 2026-09-18 20:45 UTCEG score recompute
  18. 2026-09-18 20:45 UTCVendor advisory
  19. 2026-09-18 20:45 UTCGHSA enrichment
  20. 2026-09-18 19:28 UTCEPSS rescore
  21. 2026-09-18 15:23 UTCEG score recompute
  22. 2026-09-18 15:23 UTCVendor advisory
  23. 2026-09-18 15:23 UTCGHSA enrichment
  24. 2026-09-18 14:35 UTCEG score recompute
  25. 2026-09-18 14:35 UTCVendor advisory
Show 12 more
  1. 2026-09-18 14:35 UTCGHSA enrichment
  2. 2026-09-18 13:50 UTCEG score recompute
  3. 2026-09-18 13:50 UTCVendor advisory
  4. 2026-09-18 13:50 UTCGHSA enrichment
  5. 2026-09-18 12:32 UTCEG score recompute
  6. 2026-09-18 12:32 UTCVendor advisory
  7. 2026-09-18 12:32 UTCGHSA enrichment
  8. 2026-09-17 23:25 UTCEG score recompute
  9. 2026-09-17 23:25 UTCVendor advisory
  10. 2026-09-17 23:05 UTCEG score recompute
  11. 2026-09-17 23:05 UTCVendor advisory
  12. 2026-09-17 23:04 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-85917?
CVE-2026-85917 is a high vulnerability published on September 17, 2026. Server-side request forgery (ssrf) in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.
When was CVE-2026-85917 disclosed?
CVE-2026-85917 was first published in the National Vulnerability Database on September 17, 2026, with the most recent update on September 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-85917 actively exploited?
CVE-2026-85917 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 55.0% of all scored CVEs.
What is the CVSS score of CVE-2026-85917?
CVE-2026-85917 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-85917?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-85917, 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-85917

Explore →

Is Your Infrastructure Affected by CVE-2026-85917?

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