# CVE-2026-92215: a2ui-project a2ui FileResolver file_resolver.py httpx.get server-side request forgery

> A server-side request forgery vulnerability in the a2ui FileResolver allows remote attackers to make arbitrary HTTP requests via the httpx.get function.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-c3w9-49h5-9jjq

## What is CVE-2026-92215?

CVE-2026-92215 is a medium-severity server-side request forgery vulnerability in a2ui-project a2ui, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability has been found in a2ui-project a2ui up to 0.10.7. Affected by this vulnerability is the function httpx.get of the file agent_sdks/python/a2ui_agent/src/a2ui/extensions/file_resolve/file_resolver.py of the component FileResolver. The manipulation leads to server-side request forgery. It is possible to initiate the attack remotely. The identifier of the patch is 2bb8423060308bbdea8ba468dabed4fc256d18ea. To fix this issue, it is recommended to deploy a patch.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-92215 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92215 is a medium-severity server-side request forgery vulnerability in a2ui-project a2ui, published on 16 Sep 2026. 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-2026-92215 in the wild and no public exploit code.

Affected product: a2ui-project a2ui. 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-92215/ (Markdown: https://insights.sbomify.com/CVE-2026-92215/index.md)
```

## Sources

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

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