Kraken agents incorrectly validate peer-to-peer downloaded blobs. The agents compute a CRC32 on each piece but neglect to verify the full SHA-256 digest of the content before committing it to the content-addressable cache. This incomplete integrity check (CWE-354) permits an attacker to supply forged data that passes the piece-level CRC32 checks while still altering the overall file, resulting in a cache poisoned with attacker‑chosen container image layers or manifests.

This vulnerability affects Uber's Kraken tool, which relies on peer-to-peer data exchange. All versions that use the default peer-to-peer download pipeline without proper digest verification are susceptible, and the issue is present across the entire Kraken codebase unless mitigated by a subsequent release.

The risk is high, reflected by a CVSS score of 9.1. Although the EPSS score is not available and the vulnerability is not listed in CISA's KEV catalog, the potential for remote code execution is significant because poisoned cache entries can be pulled and executed by other hosts. An attacker would need the ability to participate in the peer-to-peer path or become a malicious peer, forging CRC32 corrections to satisfy per‑piece checks while delivering arbitrary content. Deployment in environments where Kraken agents regularly exchange data with untrusted peers heightens the likelihood of exploitation.