# CVE-2026-97785: AAD App Proxy Elevation of Privilege Vulnerability


- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-5vq4-h6h5-3gjg

## What is CVE-2026-97785?

CVE-2026-97785 is a critical vulnerability in Microsoft Entra application proxy, published on 22 Oct 2026. 

### Official description

Improper authentication in AAD App Proxy allows an unauthorized attacker to elevate privileges over a network.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-97785?


## How do I fix CVE-2026-97785?

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

## Is CVE-2026-97785 being exploited?

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

Public exploit code:

- Offline Python applicability detector for CVE-2026-97785 in Microsoft Entra application proxy, with CSV/JSON inventories and auditable reports. (github_poc): https://github.com/mehmet-emir-eroglu/CVE-2026-97785

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-97785 and fix it if it is affected.

What it is: CVE-2026-97785 is a critical vulnerability in Microsoft Entra application proxy, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-97785 in the wild and no public exploit code.

Affected product: Microsoft Entra application proxy. 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-2026-97785/ (Markdown: https://insights.sbomify.com/CVE-2026-97785/index.md)
```

## Sources

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

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