Uber Kraken through 0.1.29 Path Traversal via tag parameter
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- No fix listed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-22 and the CVSS impact.
Summary
Uber Kraken through 0.1.29 fails to validate the tag parameter in the /tags/{tag} endpoint, allowing unauthenticated attackers to traverse outside the configured storage root. Attackers can use percent-encoded parent-directory segments in the tag parameter to read arbitrary files accessible to the testfs backend process.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2026-92791
- 2026-10-03 Alias added: GHSA-2jmw-fcwx-7j6h
References
More uber vulnerabilities
- TI-2026-52917 Kraken Agents Peer-to-Peer Download Cache Poisoning via Digest Verification Bypass CVSS 4.0CRITICAL 9.1
- TI-2022-23695 kraken <= 0.1.4 has an arbitrary file read vulnerability via the component testfs. CVSS 3.1HIGH 7.5
- TI-2017-09741 Hard-coded credentials in UberEATS: Uber for Food Delivery CVSS 3.0HIGH 7.5
Sources
- CVE-2026-92791 · CVE Program
- CVE-2026-92791 · NVD
- FIRST EPSS
- GHSA-2jmw-fcwx-7j6h · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences