Loading vulnerability…
CVE-2026-33747 is a path traversal vulnerability in BuildKit versions prior to 0.28.1. A custom BuildKit frontend can craft an API message that causes BuildKit to write files outside the state directory allocated to the build execution context. The flaw is exposed only where an untrusted frontend is selected through the Dockerfile syntax directive or the BuildKit syntax build argument. Trusted, well-known frontends such as the standard Dockerfile frontend are not affected.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
21 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
One of multiple Docker Engine and bundled BuildKit vulnerabilities addressed by Debian DSA-6443; the advisory collectively describes potential privilege escalation, arbitrary host file access, and authorization-policy bypass.
A path traversal vulnerability in BuildKit that allows a custom untrusted frontend to craft API messages causing files to be written outside the BuildKit state directory.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.