Sub2api
Monthly
Path traversal in Sub2API versions 0.1.135-0.1.168 allows authenticated tenants to relay API requests to arbitrary upstream endpoints using operator-owned provider credentials (ChatGPT/Codex OAuth tokens, OpenAI platform keys, or operator-configured base URLs). The POST /responses/*subpath wildcard route accepted client-controlled subpaths and concatenated them into upstream URLs without sanitization, enabling scope-changing abuse of pooled shared accounts. No public exploit code has been identified at time of analysis, but the fix is publicly documented via GitHub advisory, PR diff, and release tag - including specific bypass path examples - substantially reducing reconstruction effort for any authenticated tenant.
Improper output encoding in Sub2API AI API gateway allows injection attacks. The platform distributes AI API quotas without properly encoding output.
Path traversal in Sub2API versions 0.1.135-0.1.168 allows authenticated tenants to relay API requests to arbitrary upstream endpoints using operator-owned provider credentials (ChatGPT/Codex OAuth tokens, OpenAI platform keys, or operator-configured base URLs). The POST /responses/*subpath wildcard route accepted client-controlled subpaths and concatenated them into upstream URLs without sanitization, enabling scope-changing abuse of pooled shared accounts. No public exploit code has been identified at time of analysis, but the fix is publicly documented via GitHub advisory, PR diff, and release tag - including specific bypass path examples - substantially reducing reconstruction effort for any authenticated tenant.
Improper output encoding in Sub2API AI API gateway allows injection attacks. The platform distributes AI API quotas without properly encoding output.