# CVE-2025-59500: Azure Notification Service Elevation of Privilege Vulnerability

> An authorized attacker can elevate privileges in Azure Notification Service due to improper access control, requiring a patch.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Oct 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-x2rm-j7cc-24ph

## What is CVE-2025-59500?

CVE-2025-59500 is a high-severity vulnerability in Microsoft Azure Notification Service, published on 23 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper access control in Azure Notification Service allows an authorized attacker to elevate privileges over a network.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2025-59500?

It affects 1 product.


Products: Microsoft Azure Notification Service.

## How do I fix CVE-2025-59500?

No fix has been published for CVE-2025-59500 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-59500 being exploited?

There is no known exploitation of CVE-2025-59500 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59500 and fix it if it is affected.

What it is: CVE-2025-59500 is a high-severity vulnerability in Microsoft Azure Notification Service, published on 23 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59500 in the wild and no public exploit code.

Affected product: Microsoft Azure Notification Service. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-59500/ (Markdown: https://insights.sbomify.com/CVE-2025-59500/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-59500
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-59500
- OSV: https://osv.dev/vulnerability/CVE-2025-59500

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-59500/
Summaries are generated and may contain mistakes; the official description above is the record.