dbcve.org
Windows 11 22h2Operating system · Microsoft

CVE-2025-58731

HIGH · 7.0 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.20348.4294 / 10.0.22621.6060 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 exists in Inbox COM Objects where memory is accessed after being freed, allowing an attacker to manipulate memory and achieve arbitrary code execution locally.

MitigationApply available patches for the affected Microsoft product containing the vulnerable Inbox COM Objects; if no patch exists, consider disabling or restricting access to the vulnerable COM component until a fix is available.

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 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
Windows 11 25h2Operating system
Affected:< 10.0.26200.6899
Windows Server 2022Operating system
Affected:< 10.0.20348.4294
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1913
Windows Server 2025Operating 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. Check Windows version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the installed Windows version and build number
    Affected if The build number falls below the fixed versions: 22621.6060 (Win11 22h2), 22631.6060 (Win11 23h2), 26100.6899 (Win11 24h2/25h2 or Server 2025), 20348.4294 (Server 2022), 25398.1913 (Server 2022 23h2)
  2. Identify Inbox COM Objects
    Open Registry Editor and navigate to HKLM\SOFTWARE\Classes\CLSID looking for entries containing 'Inbox' or query COM objects using 'reg query HKLM\SOFTWARE\Classes\CLSID' and filter for Inbox-related components
    Affected if Any Inbox COM Objects are registered on the system
  3. Verify COM object instantiation
    Use PowerShell to attempt enumeration: Get-ItemProperty -Path 'HKLM:\SOFTWARE\Classes\CLSID\*' | Where-Object {$_.PsChildName -match 'Inbox'} to find registered Inbox COM components
    Affected if Inbox COM Objects are found in the registry and the Windows version is vulnerable
  4. Check for recent patches
    Run 'wmic qfe list' or 'Get-HotFix' to list installed updates, then search for Microsoft security updates released after the CVE publication date that address Inbox COM Objects
    Affected if No corresponding security patch for this CVE is installed and the version is in the affected range

You are affected if your Windows version matches one of the affected builds AND Inbox COM Objects are present on the system without the corresponding security patch installed.

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.20348.4294 / 10.0.22621.6060 / 10.0.25398.1913 or later
Fixed in 10.0.20348.429410.0.22621.606010.0.25398.1913
Interim mitigation

Apply available patches for the affected Microsoft product containing the vulnerable Inbox COM Objects; if no patch exists, consider disabling or restricting access to the vulnerable COM component until a fix is available.

Recommended fix High confidence

Windows 11 22h2/23h2/24h2/25h2: Apply the applicable cumulative update (KB) containing the fix; Windows Server 2022/2022 23h2/2025: Apply the applicable Windows Server cumulative update (KB) containing the fix. Minimum fixed builds: 10.0.22621.6060 (22h2), 10.0.22631.6061+ (23h2), 10.0.26100.6899 (2

  1. 1. Determine your current Windows version by running `winver` or checking Settings > System > About
  2. 2. For Windows 11 22h2 (builds below 10.0.22621.6060): Install the Windows 11 2024 Update (23h2) or later to receive the security fix
  3. 3. For Windows 11 23h2 (builds <= 10.0.22631.6060): Install the latest Windows 11 cumulative update from Settings > Windows Update
  4. 4. For Windows 11 24h2 (builds below 10.0.26100.6899): Install the latest Windows 11 cumulative update
  5. 5. For Windows 11 25h2 (builds below 10.0.26200.6899): Install the latest Windows 11 cumulative update
  6. 6. For Windows Server 2022 (builds below 10.0.20348.4294): Install the latest Windows Server 2022 cumulative update from Windows Update for Business or WSUS
  7. 7. For Windows Server 2022 23h2 (builds below 10.0.25398.1913): Install the latest cumulative update
  8. 8. For Windows Server 2025 (builds <= 10.0.26100.6899): Install the latest cumulative update
Caveat Standard Windows update - review Microsoft KB article for the specific update for any known issues before deployment in production environments

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

Fix this in Windows 11 22h2 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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