External risk intelligence

Kraken Agents Cache Poisoning Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-75625

The vulnerability exists in peer-to-peer agent-to-agent communication within a distributed container distribution system. While these agents communicate over the network, they are typically deployed within private, segmented internal infrastructure clusters rather than being exposed to the public internet.

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

The Kraken agents have a vulnerability where they do not properly verify downloaded content before storing it, potentially allowing malicious code to be introduced and spread across systems. This could lead to compromised container images being used within your environment. The main concern is confirming relevance and exposure.

Stored content is not verified before caching.
Malicious code could be distributed internally.
Confirm relevance and potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker can poison the cache of Kraken agents by supplying malicious content that bypasses proper verification. This occurs when agents download content via peer-to-peer connections and fail to check the content's integrity against a secure digest, instead relying on less robust checksums. Once the cache is poisoned, other hosts may retrieve and execute this compromised content.

Requires network access to agents.
Downloads content without full integrity checks.
Leads to execution of malicious code.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an attacker to poison the content-addressable cache with malicious container image layers or manifests. When supported by the advisory, these poisoned components could then be re-seeded and executed by other hosts on the network.

Malicious container images or manifests.
Cache poisoning via forged checksums.
Compromised container execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Kraken agents' peer-to-peer download mechanism is vulnerable to cache poisoning if not properly secured, potentially impacting container image integrity. Application owners, infrastructure teams, and security teams should collaborate to identify all instances of the affected technology, confirm their exposure and criticality, and plan remediation based on risk.

Application and Infrastructure teams own remediation.
Verify all Kraken agent deployments and network exposure.
Plan secure image distribution and update policies.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is Kraken and how is it used?

Kraken is a peer-to-peer container image registry and distribution system designed for large-scale environments. It facilitates fast image delivery by allowing agents within a cluster to share layers and manifests directly with one another, reducing the load on a central registry.

What does CWE-354 mean for CVE-2026-75625?

CWE-354 refers to improper validation of integrity check values. In the context of this CVE, the software relies on CRC32 checksums, which are not cryptographically secure, rather than verifying files against their SHA-256 digest. This allows an attacker to substitute malicious files that effectively mimic the expected checksum, tricking the system into trusting and caching the illegitimate data as if it were authentic.

How does an attacker trigger this cache poisoning?

An attacker triggers this by injecting malicious content into the peer-to-peer download stream. Because the agent only checks the CRC32, the attacker can supply forged CRC32 values that match their malicious payload, causing the agent to accept it. Legitimate content transfers or direct downloads from the origin registry are not affected by this specific verification flaw.

Is my environment at risk from this Kraken vulnerability?

According to Halo Surface Signal, this issue is unlikely to impact environments that keep their Kraken agents restricted to private, segmented internal infrastructure. The vulnerability primarily concerns peer-to-peer traffic; if your agents are not exposed to untrusted networks or malicious actors who can reach your internal peer-to-peer communication, the immediate risk is significantly lower.

What should I do to address this Kraken issue?

Begin by identifying all running Kraken agent instances within your infrastructure. Coordinate with your application and platform teams to evaluate their current network isolation. Since this is an integrity verification defect, prioritize monitoring for unauthorized changes in your container environment and prepare to apply future software updates that enforce SHA-256 digest validation.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.