CVE-2025-58738
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 Inbox COM Objects allows an unauthorized attacker to execute code 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 Inbox COM Objects enabling local privilege escalation through improper memory management. The vulnerability allows an unauthorized attacker to achieve code execution by exploiting freed COM object references.
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.10240.21161< 10.0.17763.7919< 10.0.19044.6456< 10.0.19045.6456< 10.0.22621.6060<= 10.0.22631.6060< 10.0.26100.6899< 10.0.26200.6899CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/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.
-
Determine Windows build numberOpen Command Prompt and run 'winver' or 'systeminfo | findstr /C:"Build"' to obtain the exact OS build versionAffected if Build number is below 10.0.10240.21161 for Windows 10 1507, below 10.0.17763.7919 for Windows 10 1809, below 10.0.19044.6456 for Windows 10 21h2, below 10.0.19045.6456 for Windows 10 22h2, below 10.0.22621.6060 for Windows 11 22h2, at or below 10.0.22631.6060 for Windows 11 23h2, below 10.0.26100.68
-
Confirm Windows release versionRun 'winver' to identify the specific Windows release (such as 1507, 1809, 21h2, 22h2, 23h2, 24h2, or 25h2) and map it to the corresponding build number thresholdAffected if The detected Windows release falls within any of the affected version ranges and its build is below the corresponding fixed build
-
Verify Inbox COM component presenceThe Inbox COM Objects are built-in Windows components and are present by default on vulnerable systems; no separate module check is required as the vulnerability exists in the core Windows COM implementationAffected if The Windows version and build are confirmed vulnerable per the version checks above - the Inbox COM component is inherently present on all Windows installations matching those versions
A system is affected if it runs any Windows 10 or 11 release with a build number lower than the security patch threshold for that specific release.
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.10240.2116110.0.17763.791910.0.19044.6456
Apply vendor-provided security patches for the affected Inbox COM component. Until patches are available, restrict local system access to trusted administrators only and monitor for anomalous process behavior indicative of UAF exploitation.
Windows 10 1507: build 10.0.10240.21161 | Windows 10 1809: build 10.0.17763.7919 | Windows 10 21h2: build 10.0.19044.6456 | Windows 10 22h2: build 10.0.19045.6456 | Windows 11 22h2: build 10.0.22621.6060 | Windows 11 23h2: build 10.0.22631.6060 or later | Windows 11 24h2: build 10.0.26100.6899 | Win
- Identify the current Windows build version by running `winver` or `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"`
- Determine which Windows version and build you are running (e.g., Windows 10 22h2, Windows 11 23h2, etc.)
- Open Settings > Windows Update and check for available updates
- Install all pending Windows security updates, which will include the patch for CVE-2025-58738
- Alternatively, manually download and install the appropriate Cumulative Update from the Microsoft Update Catalog for your specific Windows version
- After installation, restart the system to apply the security patch
- Verify the build number has been updated to the fixed version or higher by running `winver`
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58738 — 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-58738 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