# CVE-2026-18973: heshengtao super-agent-party extension_proxy Route server.py sanitize_proxy_url server-side request forgery

> Remote attackers can exploit a server-side request forgery vulnerability in the super-agent-party extension to access internal resources or bypass security controls.

- **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:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** GHSA-m39w-xf3h-v4h2

## What is CVE-2026-18973?

CVE-2026-18973 is a medium-severity server-side request forgery vulnerability in heshengtao super-agent-party, published on 6 Aug 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 heshengtao super-agent-party up to 0.4.1. The impacted element is the function sanitize_proxy_url of the file server.py of the component extension_proxy Route. The manipulation of the argument url leads to server-side request forgery. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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

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


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

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

## Is CVE-2026-18973 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18973 is a medium-severity server-side request forgery vulnerability in heshengtao super-agent-party, published on 6 Aug 2026. 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-2026-18973 exists.

Affected product: heshengtao super-agent-party. 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-18973/ (Markdown: https://insights.sbomify.com/CVE-2026-18973/index.md)
```

## Sources

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

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