dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-50159

HIGH · 7.3 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 10.0.10240.21100 / 10.0.14393.8330 or later.
See remediation →
73/100
Remediation priority · Elevated

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Use after free in Remote Access Point-to-Point Protocol (PPP) EAP-TLS allows an authorized attacker to elevate privileges locally.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A use-after-free vulnerability in the Remote Access PPP EAP-TLS implementation allows an authenticated local attacker to exploit freed memory, potentially elevating privileges to higher permission levels.

MitigationApply vendor patches for the affected PPP EAP-TLS implementation and ensure proper memory lifecycle management in the authentication module.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1507Operating system
Affected:< 10.0.10240.21100
Windows 10 1607Operating system
Affected:< 10.0.14393.8330
Windows 10 1809Operating system
Affected:< 10.0.17763.7678
Windows 10 21h2Operating system
Affected:< 10.0.19044.6216
Windows 10 22h2Operating system
Affected:< 10.0.19045.6216
Windows 11 22h2Operating system
Affected:< 10.0.22621.5768
Windows 11 23h2Operating system
Affected:< 10.0.22631.5768
Windows 11 24h2Operating system
Affected:< 10.0.26100.4851

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows version against affected builds
    Open Command Prompt and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the build number. Compare it to the affected ranges: 10.0.10240.21100 (1507), 10.0.14393.8330 (1607), 10.0.17763.7678 (1809), 10.0.19044.6216 (21h2), 10.0.19045.6216 (22h2), 10.0.22621.5768 (22h2), 10.0.22631.5768 (23h2), 10.0.26100.4851 (24h2).
    Affected if The installed build number is lower than the corresponding threshold for your Windows version.
  2. Verify Remote Access service status
    Open Services (services.msc) and check if 'Routing and Remote Access' (RRAS) service is enabled, or run 'netsh ras show state' from an elevated command prompt.
    Affected if Routing and Remote Access (RRAS) is enabled or running on an affected Windows version.
  3. Check for EAP-TLS authentication configuration
    Open Network Connections (ncpa.cpl), right-click a VPN or dial-up connection, select Properties, go to the Security tab, and examine whether Extensible Authentication Protocol (EAP) with TLS is selected or configured.
    Affected if EAP-TLS authentication method is configured on a dial-up or VPN connection on an affected system.
  4. Identify PPP-based network interfaces
    Run 'netsh interface show interface' to list all RAS connections. Check Device Manager (devmgmt.msc) under Network adapters for RAS Capable dial-up devices.
    Affected if PPP-based dial-up or RAS interfaces exist on an affected Windows version.

A system is likely affected if it runs an unpatched Windows version within the affected build ranges AND has Remote Access with PPP EAP-TLS enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.10240.21100 / 10.0.14393.8330 / 10.0.17763.7678 or later
Fixed in 10.0.10240.2110010.0.14393.833010.0.17763.7678
Interim mitigation

Apply vendor patches for the affected PPP EAP-TLS implementation and ensure proper memory lifecycle management in the authentication module.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.21100 | Windows 10 1607: 10.0.14393.8330 | Windows 10 1809: 10.0.17763.7678 | Windows 10 21h2: 10.0.19044.6216 | Windows 10 22h2: 10.0.19045.6216 | Windows 11 22h2: 10.0.22621.5768 | Windows 11 23h2: 10.0.22631.5768 | Windows 11 24h2: 10.0.26100.4851

  1. Identify the Windows version and build number by running 'winver' or 'systeminfo' in Command Prompt
  2. Navigate to the Microsoft Security Response Center (msrc.microsoft.com) and search for CVE-2025-50159
  3. Download and install the corresponding security update patch (KB number) for your Windows version from Windows Update or the Microsoft Update Catalog
  4. Restart the system after installing the patch to ensure the vulnerability is fully remediated
  5. Verify the patch installation by checking the installed updates list or running 'systeminfo' to confirm the build number matches or exceeds the fixed version for your Windows release
Caveat Security patches rarely introduce breaking changes; however, verify application compatibility and backup critical data before applying

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-50159 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-50159 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data