Quick answers
- Is CVE-2026-75625 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-75625 being exploited in the wild.
- How severe is CVE-2026-75625?
- Critical severity, with a CVSS score of 9, published 18 August 2026.
- Which products and versions are affected?
- Uber Kraken <UNKNOWN>.
- Is there a fix for CVE-2026-75625?
- 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.
- How is CVE-2026-75625 attacked?
- It is attacked over the network or from the adjacent network, in a software library.
- Am I affected by CVE-2026-75625?
- 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
The vulnerability is a cryptographic verification bypass in the blob download and caching mechanism. Kraken agents download Docker image layers (blobs) from peers via torrent-like P2P transfers and validate them using only CRC32 checksums per piece, rather than verifying the full blob against its requested SHA-256 digest before committing to the content-addressable cache. An attacker on the network path or operating a malicious peer can supply substituted blob content with forged CRC32 values that pass per-piece validation, poisoning the cache with attacker-chosen container image layers or manifests. The attack requires network access to the P2P transfer path or the ability to participate as a peer, and the poisoned content is then re-seeded and executed by other hosts in the deployment. No patch availability information is provided in the advisory.
Affected products
- Uber Kraken <UNKNOWN>
Timeline
- 2026-08-18: disclosed