Daemon crash via invalid symlink owner input
Published Oct 5, 2026 · Updated Oct 5, 2026
Denial of service in Moby Project BuildKit 0.33.0 and earlier allows attackers to crash buildkitd through a crafted frontend LLB file operation. The LLB file-operation handler accepts invalid symlink owner input instead of rejecting the malformed definition, causing a daemon panic. Exploitation requires an untrusted external frontend; the crash terminates builds on that daemon, while ordinary Dockerfile builds are unaffected.
Summary
What happened
Denial of service in Moby Project BuildKit 0.33.0 and earlier allows attackers to crash buildkitd through a crafted frontend LLB file operation. The LLB file-operation handler accepts invalid symlink owner input instead of rejecting the malformed definition, causing a daemon panic. Exploitation requires an untrusted external frontend; the crash terminates builds on that daemon, while ordinary Dockerfile builds are unaffected.
The record
- CVE
- CVE-2026-93321
- Published
- Oct 5, 2026
- Updated
- Oct 5, 2026
- Vendor
- Moby Project
- Product
- BuildKit
- Classifications
- CWE-129, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 5, 2026CVE publishedPublication date reported by the CVE source.
- Oct 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=0.33.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started