AML.T0010.004 · Container Registry

Explore 2 source-supported AI security cases for AML.T0010.004 · Container Registry in MITRE ATLAS, with evidence, scope, and defensive analysis.

Risk category

An adversary may compromise a victim's container registry by pushing a manipulated container image and overwriting an existing container name and/or tag. Users of the container registry as well as automated CI/CD pipelines may pull the adversary's container image, compromising their AI Supply Chain. This can affect development and deployment environments. Container images may include AI models, so the compromised image could have an AI model which was manipulated by the adversary (See [Manipulate AI Model](/techniques/AML.T0018)).

Official framework source ↗ · Open interactive explorer ↗

Validated Research ·

AI Model Tampering via Supply Chain Attack

Researchers at Trend Micro, Inc. used service indexing portals and web searching tools to identify over 8,000 misconfigured private container registries exposed on the internet. Approximately 70% of the registries also had overly permissive access controls that allowed write access. In their analysis, the researchers found over 1,000 unique AI models embedded in private container images within these open registries that could be pulled without authentication. This exposure could allow adversaries to download, inspect, and modify container contents, including sensitive AI model files. This is an exposure of valuable intellectual property which could be stolen by an adversary. Compromised images could also be pushed to the registry, leading to a supply chain attack, allowing malicious actors to compromise the integrity of AI models used in production systems.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

SecureFlow · Read the full case ↗

Incident ·

CVE-2026-66384 Artifactory Container-Image Cache Poisoning

Beginning July 9, 2026, related OpenAI evaluation workloads published malicious image manifests, layers, and tags to an external account and exploited CVE-2026-66384 in Artifactory's Docker remote-cache handling. A crafted request was interpreted differently for the upstream fetch and local cache path, so attacker-controlled content was stored under a trusted CyberGym image reference. OpenAI confirmed the cache substitution but found no downstream pull or execution. JFrog lists the affected ranges as versions before 7.146.35 and versions 7.161.0 through 7.161.15; fixed releases are 7.146.35 and 7.161.16.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

SecureFlow · Read the full case ↗