What is the CVSS score of EUVD-2025-17765?

EUVD-2025-17765 has a CVSS 3.1 base score of 7.8 (High). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.2%.

Which versions of Windows are affected by EUVD-2025-17765?

CVE-2025-47962 is a privilege escalation vulnerability in Windows SDK that enables authenticated local users to gain elevated system access, potentially compromising confidentiality, integrity, and…. A patch is available.

How to fix or mitigate EUVD-2025-17765?

Within 24 hours: Identify all systems running affected Windows SDK versions and assess current patch levels. Within 7 days: Apply vendor-released patch to all Windows SDK installations in development, testing, and production environments; verify patch deployment through vulnerability scanning. Within 30 days: Conduct post-patch validation testing and update change management records; review access control policies for local user account privileges.

Windows EUVD-2025-17765

| CVE-2025-47962 HIGH

Improper Access Control (CWE-284)

2025-06-10 secure@microsoft.com

Windows Privilege Escalation Microsoft Windows Software Development Kit

7.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.8 HIGH

AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Updated

Apr 16, 2026 - 06:40 EUVD-patch-fix

executive_summary

Re-analysis Queued

Apr 16, 2026 - 05:29 backfill_euvd_patch

patch_released

Patch available

Apr 16, 2026 - 05:29 EUVD

10.0.26100.4188

EUVD ID Assigned

Mar 14, 2026 - 19:49 euvd

EUVD-2025-17765

Analysis Generated

Mar 14, 2026 - 19:49 vuln.today

CVE Published

Jun 10, 2025 - 17:24 nvd

HIGH 7.8

DescriptionCVE.org

Improper access control in Windows SDK allows an authorized attacker to elevate privileges locally.

AnalysisAI

CVE-2025-47962 is an improper access control vulnerability in Windows SDK that allows an authenticated local attacker to escalate privileges without user interaction. The vulnerability affects Windows SDK components and presents a high risk due to its CVSS score of 7.8 (High severity) with high impact on confidentiality, integrity, and availability. While no active exploitation in the wild (KEV status) or public POC has been confirmed at this time, the low attack complexity and requirement for only local user privileges make this a significant priority for Windows environments.

Technical ContextAI

This vulnerability stems from CWE-284 (Improper Access Control), a fundamental authorization bypass weakness where the Windows SDK fails to properly validate or enforce access control restrictions for local users. The flaw likely exists in Windows SDK components responsible for privilege-sensitive operations or system resource access. The attack vector is local (AV:L) with low complexity (AC:L), indicating the vulnerability can be exploited through standard local system access without requiring complex manipulation. The root cause appears to be insufficient authorization checks that allow authenticated users with standard privileges to access or modify protected resources or operations intended for elevated privilege levels, bypassing the principle of least privilege.

RemediationAI

Apply Windows SDK security updates when released by Microsoft - check Microsoft Security Update Guide and Windows SDK release notes for CVE-2025-47962. 2) Prioritize patching for systems where local user account compromise is a realistic threat (multi-user systems, shared dev environments). 3) Implement compensating controls: restrict local user account creation and access, enforce strict user account access controls, implement application whitelisting for SDK tools, and monitor for unauthorized privilege escalation attempts. 4) Review and audit local user permissions on systems running Windows SDK, removing unnecessary local user accounts. 5) Monitor Windows Security event logs for privilege escalation or access control violations. 6) In high-risk environments, isolate Windows SDK usage to dedicated, hardened systems with minimal local user accounts until patches are validated and deployed.