Summary
CVE-2026-92791 is a path traversal vulnerability (CWE-22) affecting Uber Kraken, an open-source peer-to-peer Docker image/container registry, in versions through 0.1.29. The flaw resides in the /tags/{tag} endpoint, where percent-encoded parent-directory sequences in the tag parameter are not properly sanitized before being passed to the storage layer, allowing an unauthenticated remote attacker to read arbitrary files accessible to the affected backend process. The vulnerability has a HIGH severity rating and does not require authentication or user interaction to exploit.
Technical details
- Root cause: The tag-lookup path-building logic (
DockerTagPather.BlobPath) and the tag-read routes fail to canonicalize or restrict percent-encoded../(parent-directory) sequences supplied in thetagparameter before resolving a filesystem path. - Trigger conditions: An attacker sends a crafted HTTP request to the
/tags/{tag}endpoint with percent-encoded directory-traversal segments in the tag value. - Attack vector: Network-based, no authentication or privileges required, no user interaction needed (the affected endpoint is exposed without an authentication check).
- Impact: Out-of-bounds read of arbitrary files reachable by the storage backend process (notably the
testfsbackend), resulting in disclosure of sensitive files (e.g., configuration data, credentials, or other data accessible to the service account). No integrity or availability impact is indicated. - Note: Kraken’s
testfs/tag-read component has previously been affected by a similar path-traversal issue (CVE-2022-47747, fixed in versions after 0.1.4); CVE-2026-92791 indicates the underlying path-sanitization weakness persisted or was reintroduced in later releases up through 0.1.29.
Affected software
- Uber Kraken (
github.com/uber/kraken) versions 0.1.29 and earlier
Severity
- CVSS v3.1 Base Score: 7.5 (HIGH) —
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N - CVSS v4.0 Base Score: 8.7 (HIGH) —
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Mitigation and recommended actions
- Immediate: Upgrade Uber Kraken to a version beyond 0.1.29 that includes proper path canonicalization/sanitization for the
/tags/{tag}endpoint. Check the project’s official repository and release notes for the specific fixed version before upgrading. - If no patch is yet available:
- Restrict network access to Kraken’s tag-server and
testfsbackend endpoints to trusted internal networks only; do not expose these services directly to the internet. - Place an authenticating reverse proxy or API gateway in front of the affected endpoints to block unauthenticated requests.
- Add WAF/ingress rules to reject requests containing percent-encoded traversal sequences (e.g.,
%2e%2e%2f) in the tag path segment. - Run the storage backend process with the least-privileged filesystem permissions possible to limit the blast radius of any successful file read.
- Monitor access logs for the
/tags/{tag}endpoint for anomalous or encoded traversal patterns.
- Restrict network access to Kraken’s tag-server and

