← Back to the live CVE advisory feed

CVE-2026-93318: Product identification pending

Severity

7.5 (HIGH)

Vendor

DOCKER

Patch status

Unknown

Published

2026-10-05T18:17:38.080

Modified

2026-10-05T20:17:28.260

Why it matters

This matters because the affected product may allow code execution. Prioritize systems that are internet-facing or have privileged access to other infrastructure.

Recommended admin actions

• Review and patch based on exposure, asset criticality, and business impact.
• Review logs for suspicious activity related to the affected application or component.

Technical summary

A malicious image can advertise DiffIDs from another image while containing different layer contents. In affected versions, BuildKit could use the advertised DiffIDs to derive cache and snapshot identity without validating that they matched the actual layer contents. If a BuildKit daemon with shared or persistent cache first processes such a malicious image, a later build using the victim image may mount the attacker-controlled layer contents as the base image. This can allow code from the malicious image to run in the victim build, for example by replacing a commonly executed path such as /bin/sh. The attacker-controlled code may read build secrets mounted into the build, access other build resources, alter output artifacts, or hang the build. The issue affects both regular snapshotters and lazy-pulling snapshotters such as stargz.

View the official NVD record for CVE-2026-93318

CVE data is sourced from NVD/CNA records and optional enrichment. Validate against the vendor advisory before taking production action.