# CVE-2026-73079: Path traversal in sub2api

> Authenticated tenants can exploit path traversal in Sub2API to relay requests to arbitrary upstream endpoints using operator credentials.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-vrxq-qm4h-6hgg

## What is CVE-2026-73079?

CVE-2026-73079 is a high-severity path traversal vulnerability in Wei-Shaw sub2api, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Sub2API is an AI API gateway platform designed to distribute and manage API quotas from AI product subscriptions. From 0.1.135, to 0.1.168, platform API keys issued to tenants are exchanged for upstream requests made with shared provider accounts (ChatGPT/Codex OAuth, OpenAI platform keys, or an operator-configured base URL) that belong to the operator, not to the caller. The `POST /responses/*subpath` wildcard routes spliced the client-supplied subpath into the upstream URL with no validation. This lets an authenticated tenant relay requests to arbitrary upstream endpoints using pooled account credentials via a path traversal. This vulnerability is fixed in 0.1.169.

Weakness: CWE-441 (Unintended Proxy or Intermediary), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-73079 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-73079 is a high-severity path traversal vulnerability in Wei-Shaw sub2api, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-73079 in the wild and no public exploit code.

Affected product: Wei-Shaw sub2api. 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-73079/ (Markdown: https://insights.sbomify.com/CVE-2026-73079/index.md)
```

## Sources

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

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