dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-26679

HIGH · 7.8 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 10.0.10240.20978 / 10.0.14393.7969 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 RPC Endpoint Mapper Service 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 exists in the Windows RPC Endpoint Mapper Service (RpcEptMapper). An authenticated local attacker can exploit this memory corruption issue to achieve privilege escalation, potentially executing code with elevated SYSTEM-level privileges.

MitigationApply Microsoft security updates for CVE-2025-26679 as soon as they become available. If patches are unavailable or as an interim measure, restrict local access to trusted administrators and monitor for unusual processes interacting with the RPC Endpoint Mapper.

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.20978
Windows 10 1607Operating system
Affected:< 10.0.14393.7969
Windows 10 1809Operating system
Affected:< 10.0.17763.7136
Windows 10 21h2Operating system
Affected:< 10.0.19044.5737
Windows 10 22h2Operating system
Affected:< 10.0.19045.5737
Windows 11 22h2Operating system
Affected:< 10.0.22621.5189
Windows 11 23h2Operating system
Affected:< 10.0.22631.5189
Windows 11 24h2Operating system
Affected:< 10.0.26100.3775

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 and build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS"' or 'Get-ComputerInfo WindowsVersion,OsBuildNumber' in PowerShell
    Affected if The build number falls below 10.0.10240.20978 for Win10 1507, below 10.0.14393.7969 for Win10 1607, below 10.0.17763.7136 for Win10 1809, below 10.0.19044.5737 for Win10 21h2, below 10.0.19045.5737 for Win10 22h2, below 10.0.22621.5189 for Win11 22h2, below 10.0.22631.5189 for Win11 23h2, or below 1
  2. Verify RPC Endpoint Mapper service status
    Run 'Get-Service RpcEptMapper' in PowerShell or 'sc query RpcEptMapper' in Command Prompt
    Affected if The service status is Running - the vulnerability exists in this service and requires it to be active for exploitation
  3. Confirm current user context
    Run 'whoami /groups' or 'whoami /priv' to see current user privileges
    Affected if Current user has SeImpersonatePrivilege or higher privileges - this is required for the authenticated local attacker to exploit the flaw

A system is affected if it runs a Windows version with a build number lower than the fixed thresholds AND the RPC Endpoint Mapper service is running.

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.20978 / 10.0.14393.7969 / 10.0.17763.7136 or later
Fixed in 10.0.10240.2097810.0.14393.796910.0.17763.7136
Interim mitigation

Apply Microsoft security updates for CVE-2025-26679 as soon as they become available. If patches are unavailable or as an interim measure, restrict local access to trusted administrators and monitor for unusual processes interacting with the RPC Endpoint Mapper.

Recommended fix High confidence

Install the Windows Security Update for your specific version (e.g., KB5055523 for March 2025 or subsequent relevant security patches)

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which version branch you are on (e.g., 1507, 1607, 1809, 21h2, 22h2, or Windows 11 version)
  3. For Windows 10 1507: Upgrade to build 10.0.10240.20978 or later
  4. For Windows 10 1607: Upgrade to build 10.0.14393.7969 or later
  5. For Windows 10 1809: Upgrade to build 10.0.17763.7136 or later
  6. For Windows 10 21h2: Upgrade to build 10.0.19044.5737 or later
  7. For Windows 10 22h2: Upgrade to build 10.0.19045.5737 or later
  8. For Windows 11 22h2: Upgrade to build 10.0.22621.5189 or later
Caveat Standard Windows security updates typically have no breaking changes; they are cumulative patches that include bug fixes and security improvements

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26679 — 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-26679 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