dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-58734

HIGH · 7.0 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 →
73/100
Remediation priority · Elevated
No privileges

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
Use 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 confidence

A use-after-free vulnerability in Inbox COM Objects allows an unauthenticated attacker to execute arbitrary code locally on the target system. The vulnerability stems from improper memory management where memory is accessed after being freed, leading to potential code execution through controlled memory corruption.

MitigationApply available vendor patches for the affected software immediately. Until a patch is available, consider restricting access to Inbox COM Objects and monitoring for indicators of exploitation.

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Windows version and build number
    Run 'winver' from command prompt or 'systeminfo' and note the OS Name and OS Version/Build number
    Affected if The build number falls below the affected thresholds: 10.0.10240.21161 (1507), 10.0.14393.8519 (1607), 10.0.17763.7919 (1809), 10.0.19044.6456 (21h2), 10.0.19045.6456 (22h2), 10.0.22621.6060 (11 22h2), 10.0.22631.6060 (11 23h2), or 10.0.26100.6899 (11 24h2)
  2. Confirm Windows 10 release version
    Run 'winver' or check Settings > System > About to identify the specific Windows 10 release (1507, 1607, 1809, 21h2, or 22h2)
    Affected if The installed Windows 10 version matches any of the affected releases listed in the CVE and the build number is below the corresponding patch threshold
  3. Confirm Windows 11 release version
    Run 'winver' or check Settings > System > About to identify the Windows 11 release (22h2, 23h2, or 24h2)
    Affected if The installed Windows 11 version matches 22h2, 23h2, or 24h2 and the build number is below the corresponding patch threshold for that release

You are affected if your Windows version and build number match any of the affected Windows 10 or Windows 11 releases listed with a build number below the specified threshold.

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 available vendor patches for the affected software immediately. Until a patch is available, consider restricting access to Inbox COM Objects and monitoring for indicators of exploitation.

Recommended fix High confidence

Windows 10 1507: build 10.0.10240.21161 or later | Windows 10 1607: build 10.0.14393.8519 or later | Windows 10 1809: build 10.0.17763.7919 or later | Windows 10 21h2: build 10.0.19044.6456 or later | Windows 10 22h2: build 10.0.19045.6456 or later | Windows 11 22h2: build 10.0.22621.6060 or later |

  1. Open Windows Settings on the affected system
  2. Navigate to Update & Security > Windows Update
  3. Click 'Check for updates' to download and install the latest cumulative update
  4. Alternatively, manually download the appropriate update from the Microsoft Update Catalog for your specific Windows version (KB5055523 or later for Windows 10/11)
  5. Restart the system after the update is installed
  6. Verify the installed update by running 'winver' command and confirm the build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows cumulative update; no expected breaking changes for this security patch

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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