Cyber Resilience

CVE-2026-41612

Path Traversal in Microsoft Live Preview ≤ 0.4.19

Path Traversal
Published
12 May 2026
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v3.1 5.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
EPSS Score 0.0050 40th percentile
Risk Priority 43 floored blend · peak EPSS

Summary

CVE-2026-41612 is a medium-severity Path Traversal (CWE-22) vulnerability in Microsoft Live Preview. Its CVSS base score is 5.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 40th 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.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

Relative path traversal in Visual Studio Code allows an unauthorized attacker to disclose information locally.

CWE(s)
CWE-22CWE-23

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
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 →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-45731Same vendor: Microsoft
CVE-2026-32193Same vendor: Microsoft
CVE-2026-45454Same vendor: Microsoft
CVE-2004-0847Same vendor: Microsoft
CVE-2026-21227Same vendor: Microsoft
CVE-2021-40444Same vendor: Microsoft
CVE-2015-0016Same vendor: Microsoft
CVE-2025-60722Same vendor: Microsoft
CVE-2021-27065Same vendor: Microsoft
CVE-2023-31036Same vendor: Microsoft

Affected Assets

microsoft
live preview
≤ 0.4.19

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)
  • V5.3.2

Mitigating Controls (NIST 800-53 r5) AI

AC-3 Access Enforcement good match

Enforces the intended directory access authorizations that path traversal would otherwise bypass.

SI-10 Information Input Validation good match

Input validation directly neutralizes special path elements before pathname construction occurs.

AC-4 Information Flow Enforcement partial match

Information-flow rules can be configured to reject traversals that would move data outside an approved directory boundary.

AC-6 Least Privilege partial match

Least privilege reduces the impact of any unauthorized file access obtained via traversal.

SA-8 Security and Privacy Engineering Principles partial match

Secure-engineering principles require safe pathname construction and input neutralization before any file operation.

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 input validation and path sanitization that prevent relative traversal.

PR.PS-02 partial match
prevents

Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.

PR.AA-05 none match
prevents

PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.

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
finds

Security testing in development catches path traversal via static/dynamic analysis.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.

A.8.26 Application security requirements partial match
prevents

Application security requirements include rules for safe file handling and canonicalization.

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

Secure architecture principles require least-privilege file access and directory isolation.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.

A.8.3 Information access restriction partial match
mitigates

Information access restriction limits which files an application may read or write.

References