Quick answers
- Is CVE-2026-92791 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92791 being exploited in the wild.
- How severe is CVE-2026-92791?
- High severity, with a CVSS score of 7.5, published 16 September 2026.
- Which products and versions are affected?
- Uber Kraken through 0.1.29.
- Is there a fix for CVE-2026-92791?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- Am I affected by CVE-2026-92791?
- Check whether you run Uber Kraken at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Kraken through version 0.1.29 fails to properly validate the tag parameter in the /tags/{tag} endpoint, enabling a path traversal vulnerability. Attackers can use percent-encoded parent-directory sequences (e.g., ../) to escape the configured storage root and access files outside the intended directory. No authentication is required; the vulnerability is network-accessible. An unauthenticated attacker can read any file that the testfs backend process has permission to access, potentially exposing configuration files, credentials, or sensitive application data. A patch should be available in versions after 0.1.29.
Affected products
- Uber Kraken through 0.1.29
Timeline
- 2026-09-16: disclosed