CVE-2026-56857
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-56857 is a critical-severity Insecure Operation on Windows Junction / Mount Point (CWE-1386) vulnerability in Go (inferred from references). Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Steganography (T1001.002); ranked at the 41th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-95420
Vulnerability Data
On Windows, when the target of Root.Mkdir or Root.MkdirAll is a junction pointing to an empty location, the operation can create a directory at the junction target even when that target is located outside the root. This only applies to…
more
operations where the last path component is a junction (path/to/junction, but not path/junction/target).
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.3
Mitigating Controls (NIST 800-53 r5) AI
Enforcing authorizations on file/directory opens structurally blocks access via junctions that escape the intended scope.
Information-flow rules that validate the final target of a name prevent unintended data access through mount points or junctions.
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.
Secure SDLC practices directly prevent improper junction/mount-point handling during design and coding.
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.
Secure development lifecycle can mandate junction/mount-point validation during design and coding.
Application security requirements can explicitly require protection against Windows reparse-point attacks.
A.8.27 mandates security-by-design, defence-in-depth, least-privilege, distrust-external-input and hardening principles plus design reviews that can catch and block insecure junction/mount-point handling in the architecture and code, but leaves a bounded remainder (e.g. third-party libraries, runtime config, or post-deployment changes) where the flaw can still be introduced and exploited.
Secure coding standards directly address safe file/directory handling to prevent insecure junction operations.