Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🛡️
Not in CISA KEV
CRITICAL severity

CVE-2026-45499 — Azure Openai

CRITICAL

CVE-2026-45499 is a critical-severity (CVSS 9.9) Server-Side Request Forgery (SSRF) vulnerability in microsoft azure openai. No vendor fix is recorded yet; mitigation options are listed below.

Server-side request forgery (ssrf) in Azure OpenAI allows an authorized attacker to elevate privileges over a network.

Published
Updated
Affected
1 product
Patched
See advisory
Exploits
None indexed
Exploitation data as of Oct 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-45499.

EPSS Exploitation Probability

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk
0.11%0.50%0.89%1.28%0.6%0.8%0.8%0.8%Aug 26Oct 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2026-45499 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Description

Server-side request forgery (ssrf) in Azure OpenAI allows an authorized attacker to elevate privileges over a network.

Affected Products

1 product · 1 configurations
Application
azure openaimicrosoft
all

Detection & mitigation playbook

Vendor / appliance

  1. Detect

    Inventory every microsoft azure openai deployment and check each version against the affected-products list above.

  2. Remediation status

    No patch has shipped for CVE-2026-45499 yet — track the microsoft azure openai advisory for a fixed release and apply the workarounds below in the meantime.

  3. Mitigate without a patch

    Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Frequently Asked Questions

Server-side request forgery (ssrf) in Azure OpenAI allows an authorized attacker to elevate privileges over a network.
O3 Security · Runtime Protection

Is CVE-2026-45499 being exploited in your environment?

Detect and block the exploit chain at execution, on systems you cannot patch yet.

Protect my workloads How runtime protection works
CVE-2026-45499: Azure Openai SSRF (Critical 9.9)