CVE-2026-73079
Authenticated tenants can proxy arbitrary upstream requests via Sub2API path traversal.
Is CVE-2026-73079 being exploited?
Not confirmed. CVE-2026-73079 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.31% probability of exploitation in the next 30 days.
How severe is CVE-2026-73079?
CVE-2026-73079 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-73079?
Yes. A fix has been recorded for CVE-2026-73079. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-73079 affect?
CVE-2026-73079 affects Sub2API 0.1.135-0.1.168, Operator provider integrations (OpenAI, ChatGPT OAuth, Codex), Self-hosted Sub2API deployments. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-73079?
Upgrade to 0.1.169, rotate provider keys, and validate upstream URL handling.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated tenant can relay requests using operator pooled AI provider credentials to arbitrary upstream URLs enabling SSRF, data exfiltration, and quota abuse.
Immediate action required
- affected>= 0.1.135 and < 0.1.169
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.