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 — 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(high)
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
46%
KEV
Not listed

Published

July 2, 2026

Last Modified

July 28, 2026

Advisory Details (1)

Auto-updated Jul 28, 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 66× in last 7d / 262× 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 262 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 28, 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 54.4% 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.

Start Free Scan →Browse All CVEs