Authenticated credentialed upstream request relay via path traversal
Published Aug 11, 2026 · Updated Aug 11, 2026
Path traversal in Sub2API 0.1.135 through 0.1.168 allows remote authenticated users to relay credentialed requests upstream. The POST /responses/*subpath routes concatenate a decoded client-controlled suffix into the upstream URL without rejecting dot segments, then attach a pooled provider credential and return the response. A valid platform API key is required; the upstream host remains constrained, but arbitrary paths on that host can receive POST requests and disclose their responses.
Summary
What happened
Path traversal in Sub2API 0.1.135 through 0.1.168 allows remote authenticated users to relay credentialed requests upstream. The POST /responses/*subpath routes concatenate a decoded client-controlled suffix into the upstream URL without rejecting dot segments, then attach a pooled provider credential and return the response. A valid platform API key is required; the upstream host remains constrained, but arbitrary paths on that host can receive POST requests and disclose their responses.
The record
- CVE
- CVE-2026-73079
- Published
- Aug 11, 2026
- Updated
- Aug 11, 2026
- Vendor
- Wei-Shaw
- Product
- Sub2API
- Classifications
- CWE-441, CWE-22, T1210
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 11, 2026CVE publishedPublication date reported by the CVE source.
- Aug 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 0.1.135, <0.1.169
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Vendor path-traversal request exampleproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo