Uber Kraken agents fail to verify peer-to-peer downloaded blobs against their requested SHA-256 digest before committing to the content-addressable cache, relying only on CRC32 checksums for piece validation. This improper validation enables attackers on the agent-to-agent path or malicious peers to supply substituted content with forged CRC32 corrections that pass per-piece checks. Consequently, the cache can be poisoned with attacker-chosen container image layers or manifests, which are then re-seeded and executed by other hosts, potentially leading to remote code execution or other severe impacts.

The vulnerability allows attackers to poison the content-addressable cache with malicious container image layers or manifests by bypassing proper integrity checks. This can lead to execution of attacker-controlled code on hosts that consume the poisoned cache entries. The CVSS 4.0 score of 9.1 reflects the critical nature of this vulnerability with network attack vector, low attack complexity, no privileges required, no user interaction, and high impacts on confidentiality, integrity, and system availability.

No patch or official fix information is provided in the available data. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, users should consider restricting peer-to-peer communication paths or implementing additional integrity verification controls outside of Kraken agents to mitigate risk.