# CVE-2025-54914: Azure Networking Elevation of Privilege Vulnerability

> Attackers can elevate privileges within Azure Networking services, requiring immediate patching by cloud administrators.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Sep 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-68h6-9289-c2v4

## What is CVE-2025-54914?

CVE-2025-54914 is a critical vulnerability in Microsoft Networking, published on 4 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Azure Networking Elevation of Privilege Vulnerability

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Microsoft Azure Networking.

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

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

## Is CVE-2025-54914 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54914 exists.

Public exploit code:

- https://github.com/Ash1996x/CVE-2025-54914-PoC (github_poc): https://github.com/Ash1996x/CVE-2025-54914-PoC
- CVE-2025-54914 exposes a critical flaw in Azure Networking that allows attackers to escalate privileges and control routing across subnets. The article explains how a missing privilege check in the “GetRouteTable” API enables lateral movement and remote exploitation, urging immediate patching and monitoring (github_poc): https://github.com/mrk336/Azure-Networking-Privilege-Escalation-Exploit-CVE-2025-54914

## Fix prompt for AI coding agents

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

What it is: CVE-2025-54914 is a critical vulnerability in Microsoft Networking, published on 4 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54914 exists.

Affected product: Microsoft Networking. 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-54914/ (Markdown: https://insights.sbomify.com/CVE-2025-54914/index.md)
```

## Sources

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

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