CVE-2025-27475
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 · uneditedSensitive data storage in improperly locked memory in Windows Update Stack 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 confidenceThis Windows Update Stack vulnerability involves sensitive data being stored in memory that is not properly locked, allowing a locally authorized attacker to read or manipulate this data to elevate their privileges to higher integrity levels on the affected system.
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< 10.0.22621.5189< 10.0.22631.5189< 10.0.26100.3775CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Windows 11 build versionOpen Command Prompt or PowerShell and run: systeminfo | findstr /C:"OS Version" or use PowerShell: Get-ComputerInfo -Property OsName,OsVersion,OsBuildNumberAffected if The displayed build number is below 22621.5189 for Windows 11 22h2, below 22631.5189 for Windows 11 23h2, or below 26100.3775 for Windows 11 24h2
-
Confirm Windows 11 release versionRun winver or check the OsDisplayVersion from PowerShell: Get-ComputerInfo -Property OsDisplayVersion to determine if the system is 22h2, 23h2, or 24h2Affected if The system is Windows 11 22h2, 23h2, or 24h2 and the corresponding build number is below the fixed version for that release
-
Verify Windows Update component is presentConfirm the Windows Update service exists: Get-Service -Name wuauserv or check for C:\Windows\SoftwareDistribution\ folder existenceAffected if The Windows Update service is present and the OS version falls within the affected build ranges
The system is affected if it runs Windows 11 22h2, 23h2, or 24h2 with a build number lower than the fixed version for that release (22621.5189, 22631.5189, or 26100.3775 respectively).
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.22621.518910.0.22631.518910.0.26100.3775
Apply the Microsoft security update for CVE-2025-27475 through standard Windows Update channels or manual patch deployment, and verify successful installation across affected endpoints.
Windows 11 22h2: build 10.0.22621.5189 or later | Windows 11 23h2: build 10.0.22631.5189 or later | Windows 11 24h2: build 10.0.26100.3775 or later
- Open Settings > Update & Security > Windows Update
- Click 'Check for updates' to download and install the latest cumulative update
- Ensure the installed version matches or exceeds: 10.0.22621.5189 for Windows 11 22h2, 10.0.22631.5189 for Windows 11 23h2, or 10.0.26100.3775 for Windows 11 24h2
- Restart the system when prompted to complete the update installation
- Verify the installed version by running 'winver' command or checking Settings > System > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27475 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-27475 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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