CVE-2025-32726
CVE-2025-32726 is a medium-severity vulnerability in Microsoft Visual Studio Code with a CVSS 3.x base score of 6.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-284.
Key facts
- Severity: Medium (CVSS 3.x base score 6.8)
- EPSS exploit prediction: 0% (41st percentile)
- Actively exploited: Not listed in CISA KEV
- EU (EUVD) id: EUVD-2025-10833
- Weakness: CWE-284
- Affected product: Microsoft Visual Studio Code
- Published:
- Last modified:
Description
Improper access control in Visual Studio Code allows an authorized attacker to elevate privileges locally.
Frequently asked questions
- What is CVE-2025-32726?
- Improper access control in Visual Studio Code allows an authorized attacker to elevate privileges locally.
- How severe is CVE-2025-32726?
- CVE-2025-32726 has a CVSS 3.x base score of 6.8, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and user interaction. Impact on confidentiality is high, integrity high, and availability low.
- Is CVE-2025-32726 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (41st percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2025-32726?
- CVE-2025-32726 affects Microsoft Visual Studio Code. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2025-32726?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- Does CVE-2025-32726 have an EU (EUVD) identifier?
- Yes. CVE-2025-32726 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-10833.
- When was CVE-2025-32726 published?
- CVE-2025-32726 was published on 2025-04-12 and last updated on 2026-06-17.
References
Affected products (1)
- cpe:2.3:a:microsoft:visual_studio_code:*:*:*:*:*:*:*:*
More vulnerabilities in Microsoft Visual Studio Code
- CVE-2026-102238 — Critical (CVSS 9.6): Improper limitation of a pathname to a restricted directory ('path traversal') in Visual Studio Code allows an…
- CVE-2026-81376 — Critical (CVSS 9.6): Incomplete comparison with missing factors in Visual Studio Code allows an unauthorized attacker to bypass a security…
- CVE-2026-47281 — Critical (CVSS 9.6): Missing authorization in Visual Studio Code allows an unauthorized attacker to elevate privileges over a network.
- CVE-2026-70098 — High (CVSS 8.8): Missing authorization in Visual Studio Code allows an unauthorized attacker to execute code over a network.
- CVE-2026-102235 — High (CVSS 8.8): Improper encoding or escaping of output in Visual Studio Code allows an unauthorized attacker to execute code over a…
- CVE-2026-78462 — High (CVSS 8.8): Authorization bypass through user-controlled key in Visual Studio Code allows an unauthorized attacker to bypass a…
All CVEs affecting Microsoft Visual Studio Code →
Other CWE-284 (Improper Access Control) vulnerabilities
- CVE-2026-91500 — Critical (CVSS 10.0): Vulnerability in the Oracle Access Manager product of Oracle Fusion Middleware (component: Authentication Engine).…
- CVE-2026-91299 — Critical (CVSS 10.0): Vulnerability in the JD Edwards EnterpriseOne Orchestrator product of Oracle JD Edwards (component: E1 IOT Orchestrator…
- CVE-2026-91221 — Critical (CVSS 10.0): Vulnerability in the Oracle SOA Suite product of Oracle Fusion Middleware (component: Fabric Layer). Supported…
- CVE-2026-101809 — Critical (CVSS 10.0): Vulnerability in the Workflow product of Oracle E-Business Suite (component: Workflow Notification Mailer). Supported…
- CVE-2026-83944 — Critical (CVSS 10.0): Improper access control in Azure Logic Apps allows an unauthorized attacker to elevate privileges over a network.
- CVE-2026-20192 — Critical (CVSS 10.0): As part of Cisco's ongoing commitment to proactive security and product quality, the Cisco Identity Services Engine…
Browse all CWE-284 (Improper Access Control) vulnerabilities →