dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-49658

MEDIUM · 5.5 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 10.0.10240.21073 / 10.0.14393.8246 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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
Out-of-bounds read in Windows TDX.sys allows an authorized attacker to disclose information 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

Windows TDX.sys (Trust Domain Extensions) contains an out-of-bounds read vulnerability that allows a locally authorized attacker to read kernel memory beyond intended boundaries, potentially exposing sensitive information.

MitigationApply Microsoft security updates for Windows TDX.sys as they become available through Windows Update or your patch management infrastructure.

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.21073
Windows 10 1607Operating system
Affected:< 10.0.14393.8246
Windows 10 1809Operating system
Affected:< 10.0.17763.7558
Windows 10 21h2Operating system
Affected:< 10.0.19044.6093
Windows 10 22h2Operating system
Affected:< 10.0.19045.6093
Windows 11 22h2Operating system
Affected:< 10.0.22621.5624
Windows 11 23h2Operating system
Affected:< 10.0.22631.5624
Windows 11 24h2Operating system
Affected:< 10.0.26100.4652

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 if TDX.sys driver is present on the system
    Open Command Prompt or PowerShell and navigate to C:\Windows\System32\drivers\, or use: dir C:\Windows\System32\drivers\TDX.sys
    Affected if The file TDX.sys does not exist on the system (the vulnerability cannot apply without this driver)
  2. Retrieve the file version of TDX.sys
    Right-click TDX.sys, select Properties, then view the Details tab to see the File version. Alternatively, in PowerShell run: (Get-Item 'C:\Windows\System32\drivers\TDX.sys').VersionInfo
    Affected if The file version is lower than the fixed versions for your Windows release (see version ranges below)
  3. Identify your Windows version and build number
    Run 'winver' from the Run dialog, or in PowerShell run: [System.Environment]::OSVersion.Version and also run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
    Affected if Your Windows build falls within any of these affected ranges: Windows 10 1507 < 10.0.10240.21073, 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.2263
  4. Confirm TDX driver is loaded in the kernel
    Open an elevated Command Prompt and run: sc query TDX or driverquery /v | findstr TDX
    Affected if The TDX service or driver shows as RUNNING while your Windows build version is within the affected ranges listed above

You are affected if TDX.sys is present on your system AND your Windows build version is lower than the fixed version for your specific Windows release (10/11 and version such as 22h2), because the out-of-bounds read flaw exists in the driver at those versions.

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.21073 / 10.0.14393.8246 / 10.0.17763.7558 or later
Fixed in 10.0.10240.2107310.0.14393.824610.0.17763.7558
Interim mitigation

Apply Microsoft security updates for Windows TDX.sys as they become available through Windows Update or your patch management infrastructure.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.21073 | 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

  1. Identify the current Windows version by running 'winver' or 'systeminfo'
  2. Determine which Windows version category applies (1507, 1607, 1809, 21h2, 22h2, 11 22h2, 11 23h2, or 11 24h2)
  3. Apply the appropriate Windows update to reach the fixed build version for your release
  4. Verify the update was successful by checking the Windows version matches or exceeds the fixed build number
Caveat Standard Windows update risks apply - ensure backups and compatibility checks for critical systems before applying

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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