# CVE-2025-64657: Azure Application Gateway Elevation of Privilege Vulnerability

> An unauthorized attacker can exploit a stack-based buffer overflow in Azure Application Gateway to elevate privileges over the network.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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:** 26 Nov 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-w337-cfcg-vpqj

## What is CVE-2025-64657?

CVE-2025-64657 is a critical memory corruption vulnerability in Microsoft Azure App Gateway, published on 26 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stack-based buffer overflow in Azure Application Gateway allows an unauthorized attacker to elevate privileges over a network.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Microsoft Azure Application Gateway.

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

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

## Is CVE-2025-64657 being exploited?

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

## Other vulnerabilities in Microsoft Azure App Gateway

- [CVE-2025-64656](https://insights.sbomify.com/CVE-2025-64656/): Azure Application Gateway Elevation of Privilege Vulnerability (critical 9.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-64657 is a critical memory corruption vulnerability in Microsoft Azure App Gateway, published on 26 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-64657 in the wild and no public exploit code.

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

## Sources

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

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