PHP2Shell : See if you’re affected with a free external attack surface scan. Click Here > 

New CVE Detected

CVE-2026-92791 – Unauthenticated Path Traversal / Arbitrary File Read – Uber Kraken ≤ 0.1.29

Be the first to know when new zero-days emerge:

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 the tag parameter 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 testfs backend), 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 testfs backend 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.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge