CVE-2026-33748 is a path traversal vulnerability in BuildKit versions before 0.28.1. BuildKit insufficiently validates the subdirectory component supplied in a Git URL fragment. A crafted subdirectory value, including one resolving through a symbolic link, can cause a build to access files outside the checked-out Git repository root. Accessible files are constrained to the same mounted filesystem as the build context.
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.
12 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 / symlink-related file access vulnerability in BuildKit where insufficient validation of Git URL fragment subdir components can allow access to files outside the checked-out Git repository root, limited to files on the same mounted filesystem.
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.