dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-49679

HIGH · 7.8 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 10.0.10240.21073 / 10.0.14393.8246 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
Numeric truncation error in Windows Shell 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 numeric truncation error in Windows Shell allows a locally authorized attacker to exploit improper handling of numeric values that get truncated, enabling local privilege escalation from a standard user account to higher system privileges.

MitigationApply the Microsoft security update for Windows Shell to address the numeric truncation vulnerability; prioritize patching systems where standard users have local access as these are the attack vector.

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.21073
Windows 10 1607Operating system
Affected:< 10.0.14393.8246
Windows 10 1809Operating system
Affected:< 10.0.17763.7558
Windows 10 21h2Operating system
Affected:< 10.0.19044.6093
Windows 10 22h2Operating system
Affected:< 10.0.19045.6093
Windows 11 22h2Operating system
Affected:< 10.0.22621.5624
Windows 11 23h2Operating system
Affected:< 10.0.22631.5624
Windows 11 24h2Operating system
Affected:< 10.0.26100.4652

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. Identify your Windows version and build number
    Open Command Prompt or PowerShell and run 'winver' to see the version and build, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
    Affected if The build number shown is lower than the threshold for your Windows release (see step 2)
  2. Determine your Windows release and compare to affected ranges
    Match your Windows release (10 1507, 10 1607, 10 1809, 10 21h2, 10 22h2, 11 22h2, 11 23h2, or 11 24h2) against the version thresholds: 10240.21073, 14393.8246, 17763.7558, 19044.6093, 19045.6093, 22621.5624, 22631.5624, or 26100.4652 respectively
    Affected if Your build number is less than the threshold for your specific Windows release and build
  3. Confirm Windows Shell is in use
    Windows Shell (explorer.exe) is the default shell on standard Windows installations. Verify by checking that Explorer process runs under your user account when you are logged in as a standard user
    Affected if The system uses Windows Explorer as the default shell (default configuration)

Your system is affected if it runs any of the listed Windows versions with a build number below the corresponding threshold, as the numeric truncation flaw in Windows Shell can then allow a local standard user to escalate to SYSTEM privileges.

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.21073 / 10.0.14393.8246 / 10.0.17763.7558 or later
Fixed in 10.0.10240.2107310.0.14393.824610.0.17763.7558
Interim mitigation

Apply the Microsoft security update for Windows Shell to address the numeric truncation vulnerability; prioritize patching systems where standard users have local access as these are the attack vector.

Recommended fix High confidence

Install the Microsoft security update for CVE-2025-49679 which brings Windows Shell to the fixed build numbers: 10.0.10240.21073 (1507), 10.0.14393.8246 (1607), 10.0.17763.7558 (1809), 10.0.19044.6093 (21h2), 10.0.19045.6093 (22h2), 10.0.22621.5624 (11 22h2), 10.0.22631.5624 (11 23h2), 10.0.26100.46

  1. Identify the current Windows version and build number by running 'winver' or 'systeminfo' in command prompt
  2. Determine which affected version range your current build falls into from the CVE listing
  3. Apply the appropriate Windows Security Update that addresses CVE-2025-49679. For most systems, this will be delivered via Windows Update (Settings > Update & Security > Windows Update > Check for updates)
  4. For enterprise environments, deploy the update through WSUS, Microsoft Update Catalog, or your patch management solution
  5. After update installation, verify the build number matches or exceeds the fixed version for your Windows release (e.g., 10.0.10240.21073 for 1507, 10.0.26100.4652 for 24h2)
  6. Reboot the system as required to complete the update installation
Caveat Standard Windows update with minimal risk; as a local privilege escalation fix, it should be prioritized. Some older versions (1507, 1607) may be out of mainstream support and require extended support updates.

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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