CVE-2026-45499

CRITICALPre-NVD 9.99.9
EchelonGraph scoreMEDIUM 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 — 4 sources updated this week
9.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.9Exploit: 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 OpenAI allows an authorized attacker to elevate privileges over a network.

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

Published

July 2, 2026

Last Modified

September 9, 2026

Advisory Details (1)

Auto-updated Sep 9, 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(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 21× in last 7d / 216× 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 660 total refreshes for this CVE.

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

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 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-45499 actively exploited?
CVE-2026-45499 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 46.2% of all scored CVEs.
What is the CVSS score of CVE-2026-45499?
CVE-2026-45499 has a CVSS v4.0 base score of 9.9 (CNA self-assessment; NVD's own analysis pending).
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.