{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-73079 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-73079 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-73079 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-73079 in the wild and no public exploit code.\n\nAffected product: Wei-Shaw sub2api. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-73079/ (Markdown: https://insights.sbomify.com/CVE-2026-73079/index.md)","id":"CVE-2026-73079","markdown":"https://insights.sbomify.com/CVE-2026-73079/index.md","name":"CVE-2026-73079","record":{"aliases":["GHSA-vrxq-qm4h-6hgg"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"AI API gateway","requires_auth":"low_privilege","summary":"Authenticated tenants can exploit path traversal in Sub2API to relay requests to arbitrary upstream endpoints using operator credentials.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-441","name":"Unintended Proxy or Intermediary"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Path traversal in sub2api","id":"CVE-2026-73079","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"SeaweedFS: Unauthenticated SSRF with response read-back via VolumeServer.FetchAndWriteNeedle","id":"CVE-2026-73080"},"packages":[],"prev":{"headline":"Vim: Arbitrary Code Execution via Netrw Menu Construction","id":"CVE-2026-73078"},"products":["sub2api"],"published":"2026-08-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-11","vendors":["Wei-Shaw"]},"summary":"Authenticated tenants can exploit path traversal in Sub2API to relay requests to arbitrary upstream endpoints using operator credentials.","url":"https://insights.sbomify.com/CVE-2026-73079/"}