CVE-2026-15788: WCOW cache mount source selector resolves NTFS junctions outside of cache root
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.41% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No special conditions are required; it is repeatable.
- Fixed version: moby BuildKit 0.31.2.
Low priority for now. Upgrade to moby BuildKit 0.31.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
BuildKit's cache mount source= selector on Windows Container on Windows (WCOW) workers does not detect NTFS directory junctions placed inside the cache root. A build authored by an untrusted user on a WCOW-configured BuildKit daemon can read arbitrary host files reachable to the BuildKit daemon process.
- Published
- Jul 20, 2026
- Updated
- Oct 24, 2026
- EPSS
- 0.4% · 35th percentile
- CWE
- CWE-59
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Docker
- 5.6
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| mobyproject | buildkit | cpe:2.3:a:mobyproject:buildkit |
Using buildkit? Add it to your stack and be the first to know about CVEs like this one. (Docker)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- mobyproject buildkitbefore 0.31.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Docker). Independent of NVD's CPE analysis and usually ahead of it.
moby BuildKit
- before 0.31.2affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Red Hat:hummingbird:1 | buildah | before 0:1.44.0-3.2.hum1 | 0:1.44.0-3.2.hum1 |
| Red Hat:hummingbird:1 | buildah | before 0:1.45.0-2.hum1 | 0:1.45.0-2.hum1 |
| Red Hat:hummingbird:1 | buildah-tests | before 0:1.44.0-3.2.hum1 | 0:1.44.0-3.2.hum1 |
| Red Hat:hummingbird:1 | podman | before 0:6.0.2-2.1.hum1 | 0:6.0.2-2.1.hum1 |
| Red Hat:hummingbird:1 | podman-docker | before 0:6.0.2-2.1.hum1 | 0:6.0.2-2.1.hum1 |
| Red Hat:hummingbird:1 | podman-machine | before 0:6.0.2-2.1.hum1 | 0:6.0.2-2.1.hum1 |
| Red Hat:hummingbird:1 | podman-remote | before 0:6.0.2-2.1.hum1 | 0:6.0.2-2.1.hum1 |
| Red Hat:hummingbird:1 | podman-tests | before 0:6.0.2-2.1.hum1 | 0:6.0.2-2.1.hum1 |
| Red Hat:hummingbird:1 | podmansh | before 0:6.0.2-2.1.hum1 | 0:6.0.2-2.1.hum1 |
| Red Hat:hummingbird:1 | trivy | before 0:0.72.0-0.1.2.hum1 | 0:0.72.0-0.1.2.hum1 |
Same product
mobyproject: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-23653BuildKit interactive containers API does not validate entitlements check40Plan
- CVE-2026-33747BuildKit vulnerable to malicious frontend causing file escape outside of storage root39Monitor
- CVE-2024-23652BuildKit possible host system access from mount stub cleaner37Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-23651Jan 31, 2024 · BuildKit possible race condition with accessing subpaths from cache mounts29Monitor
- ← EarlierCVE-2026-33748Mar 27, 2026 · BuildKit Git URL subdir component can cause access to restricted files32Monitor
- Later →CVE-2026-15789Jul 21, 2026 · Malicious client can bypass destination directory validation on local sources upload27Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| moby BuildKit | 0.31.2 | Vendor (CNA) |
| red hat:buildah | 0:1.44.0-3.2.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:buildah-tests | 0:1.44.0-3.2.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:podman | 0:6.0.2-2.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:podman-docker | 0:6.0.2-2.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:podman-machine | 0:6.0.2-2.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:podman-remote | 0:6.0.2-2.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:podman-tests | 0:6.0.2-2.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:podmansh | 0:6.0.2-2.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:trivy | 0:0.72.0-0.1.2.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Junyi Liu (mosskappa)finder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- A
- Scope
- X
Weakness class (CWE)
CWE-59 · Improper Link Resolution Before File Access ('Link Following')CVSS vector
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
- Obfuscated Files or Information: HTML SmugglingT1027.006
- Obfuscated Files or Information: Embedded PayloadsT1027.009
- Boot or Logon Autostart Execution:Shortcut ModificationT1547.009
- Hide Artifacts: Resource ForkingT1564.009
- Hijack Execution Flow: Executable Installer File Permissions WeaknessT1574.005
- Hijack Execution Flow: Services File Permissions WeaknessT1574.010
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.