Cyber Resilience

CVE-2026-15788

Published
20 July 2026
Modified
21 July 2026
CVSS Score v4 5.6
Click a component to see what it means
Raw vectorCVSS: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
EPSS Score 0.0014 4th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-15788 is a medium-severity Link Following (CWE-59) vulnerability. Its CVSS base score is 5.6 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 4th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

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…

more

reachable to the BuildKit daemon process.

CWE(s)
CWE-59

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
attack.mitre.org →
Why these techniques?

Vulnerability enables direct unauthorized read access to arbitrary host files via malicious build input exploiting link following in cache mounts.

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-56692Shared CWE-59
CVE-2026-46468Shared CWE-59
CVE-2026-58403Shared CWE-59
CVE-2026-28866Shared CWE-59
CVE-2026-49180Shared CWE-59
CVE-2025-24103Shared CWE-59
CVE-2026-5061Shared CWE-59
CVE-2026-9804Shared CWE-59
CVE-2026-16077Shared CWE-59
CVE-2026-50135Shared CWE-59

Affected Assets

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V15.4.2

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require code to validate paths and avoid unsafe link following.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing can detect link-following flaws before release.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC practices can mandate link-resolution checks and canonicalization before file access.

A.8.26 Application security requirements partial match
prevents

Application security requirements can explicitly require safe handling of symbolic links and path traversal.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include input validation and safe file-access design patterns.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly address canonicalization and symlink attacks during implementation.

A.8.3 Information access restriction none match
none

Access-control rules can limit which files are reachable, reducing exposure to malicious links.

References