Path Traversal in Sub2API (CVE-2026-73079)
Summary
Path traversal in Sub2API (CVE-2026-73079). Confidential information can be exposed externally. Exploitable via POST /responses/. Mitigation: upgrade to 0.1.169 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-73079 has been found in Sub2API.
Attackers can target a specific entry point like POST /responses/ over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.5/10.
What to do: upgrade Sub2API to 0.1.169 or later.
If unsure, ask your IT team or search "Sub2API CVE-2026-73079" on the vendor's site.
CVE-2026-73079 (Sub2API) — CWE-22 / CVSS v3 8.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /responses/
Patched: 0.1.169 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in Sub2API. Attackers reach the vulnerable code path via POST /responses/.
Check the vendor advisory for the affected versions of Sub2API. Attack surface: POST /responses/.
Severity: High (CVSS 8.5/10). Confidential information can be exposed externally.
Update to 0.1.169.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /responses/ requests with malformed payloads or SQL meta-characters. Run grep -r 'Sub2API' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Sub2API' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Sub2APIを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /responses/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /responses/への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade Sub2API to 0.1.169ステージング環境で 0.1.169 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /responses/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。