CVE-2025-49726
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 · uneditedUse after free in Windows Notification 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 confidenceUse-after-free vulnerability in the Windows Notification component that allows a locally authenticated attacker to corrupt memory and elevate privileges to higher permission levels.
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.14393.8246< 10.0.17763.7558< 10.0.19044.6093< 10.0.19045.6093< 10.0.22621.5624< 10.0.22631.5624< 10.0.26100.4652< 10.0.14393.8246CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Windows versionRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the installed Windows version and build numberAffected if The installed version and build are lower than any of these thresholds: Windows 10 1607 < 10.0.14393.8246, Windows 10 1809 < 10.0.17763.7558, Windows 10 21h2 < 10.0.19044.6093, Windows 10 22h2 < 10.0.19045.6093, Windows 11 22h2 < 10.0.22621.5624, Windows 11 23h2 < 10.0.22631.5624, Windows 11 24h2 <
-
Identify Windows Notification componentCheck for the presence of Windows notification-related DLLs in the system, particularly in the Windows notification folder. Run 'dir C:\Windows\System32\*notif*' and 'dir C:\Windows\System32\*toast*' to list notification-related filesAffected if The notification DLLs exist on the system (the component is present, making the vulnerability potentially exploitable)
-
Verify notification service statusOpen Services console (services.msc) and locate the Windows Notification Service or check via command: 'sc query wercplsupport' or similar notification-related servicesAffected if The Windows Notification service is running or available on the system
-
Check for privilege elevation indicatorsReview Security event logs for Event ID 4672 (Special privileges assigned) or 4624 (An account was successfully logged on) combined with unusual process creation events related to notification componentsAffected if Unusual audit events involving notification processes or unexpected privilege escalation patterns are found
The system is affected if it runs any Windows version listed above with a build number below the specified threshold and has the Windows Notification component present and accessible.
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.14393.824610.0.17763.755810.0.19044.6093
Apply Microsoft security updates for Windows when released; limit local access to trusted accounts; implement least-privilege policies to reduce attack surface.
Windows 10 1607: 10.0.14393.8246 | Windows 10 1809: 10.0.17763.7558 | Windows 10 21h2: 10.0.19044.6093 | Windows 10 22h2: 10.0.19045.6093 | Windows 11 22h2: 10.0.22621.5624 | Windows 11 23h2: 10.0.22631.5624 | Windows 11 24h2: 10.0.26100.4652 | Windows Server 2016: 10.0.14393.8246
- 1. Identify the current Windows version and build by running 'winver' or 'systeminfo' in Command Prompt
- 2. Determine which Windows release version corresponds to your current build (e.g., 1607, 1809, 21h2, 22h2, 23h2, 24h2, or Server 2016)
- 3. Check if your current build number is lower than the fixed version for your release (see upgrade_path for specific build numbers)
- 4. If vulnerable, apply the appropriate Windows update via Settings > Update & Security > Windows Update, or use Windows Server Update Services (WSUS) for server environments
- 5. Alternatively, download and install the specific security update from the Microsoft Update Catalog matching your Windows version (search for CVE-2025-49726)
- 6. After installation, restart the system to apply the security patch
- 7. Verify the fix by checking that the build number matches or exceeds the fixed version for your release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49726 — 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-49726 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