Cyber Resilience

CVE-2025-49714

Microsoft Python ≤ 2025.8.1

Published
08 July 2025
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v3.1 7.8
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:H/A:H
EPSS Score 0.0040 33th percentile
Risk Priority 58 floored blend · peak EPSS

Summary

CVE-2025-49714 is a high-severity Trust Boundary Violation (CWE-501) vulnerability in Microsoft Python. Its CVSS base score is 7.8 (High).

Operationally, ranked at the 33th 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-4 (Information Flow Enforcement) and AC-16 (Security and Privacy Attributes) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A06:2025 Insecure Design

EU & UK References

Vulnerability Data

Trust boundary violation in Visual Studio Code - Python extension allows an unauthorized attacker to execute code locally.

CWE(s)
CWE-501

Related Threats

CVEs Like This One

CVE-2024-49050Same product: Microsoft Python
CVE-2026-33828Same vendor: Microsoft
CVE-2023-28597Same vendor: Microsoft
CVE-2020-0986Same vendor: Microsoft
CVE-2024-29982Same vendor: Microsoft
CVE-2024-38228Same vendor: Microsoft
CVE-2025-21213Same vendor: Microsoft
CVE-2024-49011Same vendor: Microsoft
CVE-2024-43646Same vendor: Microsoft
CVE-2024-49039Same vendor: Microsoft

Affected Assets

microsoft
python
≤ 2025.8.1

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

AC-4 Information Flow Enforcement good match

Information flow enforcement directly stops trusted and untrusted data from being combined by applying rules that govern allowable data movements and combinations.

AC-16 Security and Privacy Attributes partial match

Associating explicit security attributes with data objects enables enforcement mechanisms that keep trust levels from being mixed inside structures.

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-development practices (coding standards, reviews, validation) directly prevent mixing trusted and untrusted data inside the same structures.

ID.AM-03 partial match
prevents

Documented data-flow representations make trust boundaries explicit and help surface mixing of trusted/untrusted data.

PR.IR-01 partial match
prevents

Logical segmentation and access controls enforce separation between trust domains, reducing the chance of co-mingled data structures.

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.27 Secure system architecture and engineering principles mostly match
prevents

Secure architecture principles require explicit trust zones and data segregation, mitigating mixing of trusted/untrusted data.

A.8.28 Secure coding mostly match
prevents

Secure coding standards can enforce input validation and data tagging, but do not guarantee architectural separation.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates separation of trusted and untrusted data flows, directly preventing mixing in the same structure.

A.8.26 Application security requirements partial match
prevents

Application security requirements include explicit trust-boundary definitions and data classification at interfaces.

A.8.22 Segregation of networks none match
none

Network segregation reduces external mixing but does not address internal data-structure trust violations.

A.8.3 Information access restriction none match
none

Information access restriction limits who sees data but does not prevent mixing trusted and untrusted data within structures.

References