dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-59275

HIGH · 7.8 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.10240.21161 / 10.0.14393.8519 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
Improper validation of specified type of input in Windows Authentication Methods 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

This is a local privilege escalation vulnerability in Windows Authentication Methods caused by improper validation of input. An authorized attacker (already having some local access) can exploit improper input handling in the Windows authentication subsystem to elevate their privileges to higher-privileged accounts. The vulnerability resides in how Windows validates input within authentication-related components.

MitigationApply Microsoft security patches for CVE-2025-59275 immediately upon release. In the interim, limit local user privileges to the minimum necessary and monitor for suspicious authentication activity.

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.21161
Windows 10 1607Operating system
Affected:< 10.0.14393.8519
Windows 10 1809Operating system
Affected:< 10.0.17763.7919
Windows 10 21h2Operating system
Affected:< 10.0.19044.6456
Windows 10 22h2Operating system
Affected:< 10.0.19045.6456
Windows 11 22h2Operating system
Affected:< 10.0.22621.6060
Windows 11 23h2Operating system
Affected:< 10.0.22631.6060
Windows 11 24h2Operating system
Affected:< 10.0.26100.6899

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. Determine Windows version and build number
    Run 'winver' or 'systeminfo' from command prompt and note the OS Name and OS Version/Build Number fields
    Affected if The displayed build number is lower than the threshold for your Windows version (see version-specific thresholds below)
  2. Identify specific Windows release
    Check the Windows version from winver output (e.g., 1507, 1607, 1809, 21h2, 22h2) or systeminfo OS Description field
    Affected if Your specific release version matches one of the affected versions listed and the build number is below its threshold
  3. Compare build against thresholds
    Match your detected release and build to: Windows 10 1507 < 10.0.10240.21161, 1607 < 10.0.14393.8519, 1809 < 10.0.17763.7919, 21h2 < 10.0.19044.6456, 22h2 < 10.0.19045.6456; Windows 11 22h2 < 10.0.22621.6060, 23h2 < 10.0.22631.6060, 24h2 < 10.0.26100.6899
    Affected if Your installed build number falls below the threshold for your detected Windows release
  4. Verify patch installation via registry
    Query registry key 'HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version' using 'reg query' command
    Affected if The installed version string is lower than the fixed build for your Windows release

You are affected if your Windows version matches any of the affected releases listed and your installed build number is below the specified threshold for that release.

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.21161 / 10.0.14393.8519 / 10.0.17763.7919 or later
Fixed in 10.0.10240.2116110.0.14393.851910.0.17763.7919
Interim mitigation

Apply Microsoft security patches for CVE-2025-59275 immediately upon release. In the interim, limit local user privileges to the minimum necessary and monitor for suspicious authentication activity.

Recommended fix High confidence

Apply the corresponding security update for your Windows version: Windows 10 1507 to build 10.0.10240.21161, Windows 10 1607 to build 10.0.14393.8519, Windows 10 1809 to build 10.0.17763.7919, Windows 10 21h2 to build 10.0.19044.6456, Windows 10 22h2 to build 10.0.19045.6456, Windows 11 22h2 to buil

  1. Check current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Open Settings > Windows Update > Check for updates
  3. Install all available security updates from Microsoft Update
  4. Restart the system when prompted to complete the installation
  5. Alternatively, manually download and install the specific security update for this CVE from the Microsoft Update Catalog
Caveat Standard Windows security update with no expected breaking changes; apply as part of regular patch maintenance

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 / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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