CVE-2026-45499

CRITICALPre-NVD 9.99.9
EchelonGraph scoreHIGH confidence

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

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

CVSS v3
9.9
EG Score
9.9(high)
EPSS
45.5%
KEV
Not listed

Published

July 2, 2026

Last Modified

July 7, 2026

Advisory Details (1)

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

Vendor Advisories for CVE-2026-45499(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 84× in last 7d / 84× 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-07 05:34 UTCEG score recompute
  2. 2026-07-07 05:34 UTCVendor advisory
  3. 2026-07-07 05:33 UTCGHSA enrichment
  4. 2026-07-07 01:40 UTCEG score recompute
  5. 2026-07-07 01:40 UTCVendor advisory
  6. 2026-07-07 01:40 UTCGHSA enrichment
  7. 2026-07-06 21:46 UTCEG score recompute
  8. 2026-07-06 21:46 UTCVendor advisory
  9. 2026-07-06 21:46 UTCGHSA enrichment
  10. 2026-07-06 17:52 UTCEG score recompute
  11. 2026-07-06 17:52 UTCVendor advisory
  12. 2026-07-06 17:52 UTCGHSA enrichment
  13. 2026-07-06 16:27 UTCEPSS rescore
  14. 2026-07-06 13:55 UTCEG score recompute
  15. 2026-07-06 13:55 UTCVendor advisory
  16. 2026-07-06 13:55 UTCGHSA enrichment
  17. 2026-07-06 10:02 UTCEG score recompute
  18. 2026-07-06 10:02 UTCVendor advisory
  19. 2026-07-06 10:02 UTCGHSA enrichment
  20. 2026-07-06 06:06 UTCEG score recompute
  21. 2026-07-06 06:06 UTCVendor advisory
  22. 2026-07-06 06:05 UTCGHSA enrichment
  23. 2026-07-06 02:23 UTCEPSS rescore
  24. 2026-07-06 02:10 UTCEG score recompute
  25. 2026-07-06 02:10 UTCVendor advisory
Show 59 more
  1. 2026-07-06 02:10 UTCGHSA enrichment
  2. 2026-07-05 22:17 UTCEG score recompute
  3. 2026-07-05 22:17 UTCVendor advisory
  4. 2026-07-05 22:17 UTCGHSA enrichment
  5. 2026-07-05 18:23 UTCEG score recompute
  6. 2026-07-05 18:23 UTCVendor advisory
  7. 2026-07-05 18:23 UTCGHSA enrichment
  8. 2026-07-05 14:30 UTCEG score recompute
  9. 2026-07-05 14:30 UTCVendor advisory
  10. 2026-07-05 14:30 UTCGHSA enrichment
  11. 2026-07-05 10:36 UTCEG score recompute
  12. 2026-07-05 10:36 UTCVendor advisory
  13. 2026-07-05 10:36 UTCGHSA enrichment
  14. 2026-07-05 06:42 UTCEG score recompute
  15. 2026-07-05 06:42 UTCVendor advisory
  16. 2026-07-05 06:42 UTCGHSA enrichment
  17. 2026-07-05 02:48 UTCEG score recompute
  18. 2026-07-05 02:48 UTCVendor advisory
  19. 2026-07-05 02:47 UTCGHSA enrichment
  20. 2026-07-05 02:30 UTCEPSS rescore
  21. 2026-07-04 22:54 UTCEG score recompute
  22. 2026-07-04 22:54 UTCVendor advisory
  23. 2026-07-04 22:54 UTCGHSA enrichment
  24. 2026-07-04 19:00 UTCEG score recompute
  25. 2026-07-04 19:00 UTCVendor advisory
  26. 2026-07-04 19:00 UTCGHSA enrichment
  27. 2026-07-04 15:07 UTCEG score recompute
  28. 2026-07-04 15:07 UTCVendor advisory
  29. 2026-07-04 15:07 UTCGHSA enrichment
  30. 2026-07-04 11:14 UTCEG score recompute
  31. 2026-07-04 11:14 UTCVendor advisory
  32. 2026-07-04 11:14 UTCGHSA enrichment
  33. 2026-07-04 07:21 UTCEG score recompute
  34. 2026-07-04 07:21 UTCVendor advisory
  35. 2026-07-04 07:20 UTCGHSA enrichment
  36. 2026-07-04 03:25 UTCEG score recompute
  37. 2026-07-04 03:25 UTCVendor advisory
  38. 2026-07-04 03:25 UTCGHSA enrichment
  39. 2026-07-03 23:31 UTCEG score recompute
  40. 2026-07-03 23:31 UTCVendor advisory
  41. 2026-07-03 23:31 UTCGHSA enrichment
  42. 2026-07-03 19:38 UTCEG score recompute
  43. 2026-07-03 19:38 UTCVendor advisory
  44. 2026-07-03 19:38 UTCGHSA enrichment
  45. 2026-07-03 15:45 UTCEG score recompute
  46. 2026-07-03 15:45 UTCVendor advisory
  47. 2026-07-03 15:45 UTCGHSA enrichment
  48. 2026-07-03 11:52 UTCEG score recompute
  49. 2026-07-03 11:52 UTCVendor advisory
  50. 2026-07-03 11:51 UTCGHSA enrichment
  51. 2026-07-03 07:54 UTCEG score recompute
  52. 2026-07-03 07:54 UTCVendor advisory
  53. 2026-07-03 07:54 UTCGHSA enrichment
  54. 2026-07-03 04:00 UTCEG score recompute
  55. 2026-07-03 04:00 UTCVendor advisory
  56. 2026-07-03 04:00 UTCGHSA enrichment
  57. 2026-07-03 00:07 UTCEG score recompute
  58. 2026-07-03 00:07 UTCVendor advisory
  59. 2026-07-03 00:06 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-45499?
CVE-2026-45499 is a critical vulnerability published on July 2, 2026. Server-side request forgery (ssrf) in Azure OpenAI allows an authorized attacker to elevate privileges over a network.
When was CVE-2026-45499 disclosed?
CVE-2026-45499 was first published in the National Vulnerability Database on July 2, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45499 actively exploited?
CVE-2026-45499 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 45.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-45499?
CVE-2026-45499 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2026-45499?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45499, 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-45499

Explore →

Is Your Infrastructure Affected by CVE-2026-45499?

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