CVE-2026-102231
Raw vector
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/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-102231 is a high-severity Improper Resolution of Path Equivalence (CWE-41) vulnerability. Its CVSS base score is 7.7 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Steganography (T1001.002); ranked at the 30th 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 SI-10 (Information Input Validation) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-99036
Vulnerability Data
Improper resolution of path equivalence in Visual Studio Code allows an unauthorized attacker to bypass a security feature locally.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Proper enforcement of file access authorizations structurally blocks disclosure when equivalent paths are presented.
Input validation of file paths directly rejects or normalizes the special-character manipulations that create equivalent names.
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.
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 includes path-handling requirements that reduce equivalence-based disclosure.
Application security requirements can mandate canonicalization and input validation to block path equivalence.
A.8.27 mandates security-by-design principles (least privilege, default-deny, distrust-external-input, security-oriented design reviews, hardening) that reach a minority slice of path-equivalence cases when applied to file-system or input-handling layers, but most CWE-41 instances arise from un-reviewed custom path canonicalization logic that the clause does not itself eliminate or block from exploitation.
Secure coding standards directly require canonical path resolution and input sanitization to prevent equivalence attacks.
Security testing can detect path-equivalence flaws before release, partially fulfilling the control.