Patch tracker / CVE reference / CVE-2026-45499

CVE-2026-45499

An Elevation of Privilege vulnerability affecting Azure Open AI.

Risk summary

Critical

9.9

CVSS v3 base

Critical

Severity

Not listed

Actively exploited

Critical severity Microsoft vulnerability, CVSS 9.9.

Senserva AI read on CVE-2026-45499 How to fix CVE-2026-45499 Change history Admin questions

Senserva AI Opinion for CVE-2026-45499

This is a Critical (CVSS 9.9) elevation of privilege flaw in Azure OpenAI, a cloud service, meaning the fix is applied by Microsoft on the service side rather than through a patch you deploy. Anyone using Azure OpenAI resources under their subscription is exposed, and the near maximum score suggests an attacker could gain privileges across tenant boundaries or against service identities. It is not in CISA KEV and has no known ransomware use, but the severity warrants prompt verification.

Do this: Review your Azure OpenAI resource role assignments and managed identity permissions now, and confirm Microsoft's service advisory for any customer-side mitigation steps.

AI-generated from public data, 2026-07-21. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2026-45499

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I am an IT admin assessing a vulnerability. Facts for CVE-2026-45499 (source: https://senserva.com/cve/CVE-2026-45499.html, data from MSRC, CISA KEV and NVD, refreshed once a day (early morning US Central)):
- CVE-2026-45499: Critical severity Microsoft vulnerability, CVSS 9.9
- Azure OpenAI Elevation of Privilege Vulnerability
- Actively exploited (CISA KEV): no
- Affected: Azure Open AI
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) What to patch or mitigate first. 4) How to check whether my devices are exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Schedule normally

No exploitation observed: not in the CISA KEV catalog, EPSS under 1%.

No vendor fix is mapped yet. This page refreshes daily and will name the patch the day one is published.

Do this now: Deploy with your normal update cycle. This page refreshes daily; the verdict changes the day the data does.

Updated September 8, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Full tracking and change history for CVE-2026-45499

Published: 2026-07-02
Last revised: 2026-07-02
Changes tracked: 1

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

How to fix CVE-2026-45499

Apply the latest Microsoft security update for the affected product. Most environments deliver it automatically through Intune update rings, Windows Update for Business, Windows Autopatch, or WSUS; for a manual install, download from the Microsoft Update Catalog. The MSRC advisory lists the exact patched build per product.

Microsoft MSRC advisory NVD detail

Common questions about CVE-2026-45499

Is CVE-2026-45499 actively exploited?

It is not currently listed in the CISA Known Exploited Vulnerabilities catalog. That can change: unexploited CVEs regularly get weaponized months after disclosure, which is why patching on your normal cadence matters.

What fixes CVE-2026-45499?

Microsoft ships the fix in its security updates. Apply the latest cumulative or security update for the affected product through Windows Update, Intune, Windows Update for Business, or the Microsoft Update Catalog, and see the MSRC advisory below for the exact build.

Which products are affected by CVE-2026-45499?

Azure Open AI.

Can I ask my own AI about CVE-2026-45499?

Yes. This page includes a free, ready-to-paste AI prompt with CVE-2026-45499's key facts: severity, CVSS, CISA KEV status, and the affected products. Copy it into Claude, ChatGPT, or Copilot for a triage plan.

Scope and sources

Affected products

Azure Open AI

Authoritative references

CVE record NVD detail Microsoft MSRC

Every Microsoft CVE and the patches that fix it, ranked by real-world risk: the Microsoft Patch Tracker. The full searchable CVE reference: CVE and vulnerability management.