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 26, 2026

Advisory Details (1)

Auto-updated Jul 26, 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 24× 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 216 total refreshes for this CVE.

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