dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-29837

MEDIUM · 5.5 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 10.0.10240.21014 / 10.0.14393.8066 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
Improper link resolution before file access ('link following') in Windows Installer 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

This is a link following (symlink) vulnerability in Windows Installer where the software does not properly resolve symbolic links before accessing files. An authorized local attacker could exploit this to read sensitive files they should not have access to, leading to information disclosure.

MitigationApply the Microsoft security update for CVE-2025-29837 through Windows Update or manual patch deployment to resolve the improper link resolution in Windows Installer.

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.21014
Windows 10 1607Operating system
Affected:< 10.0.14393.8066
Windows 10 1809Operating system
Affected:< 10.0.17763.7314
Windows 10 21h2Operating system
Affected:< 10.0.19044.5854
Windows 10 22h2Operating system
Affected:< 10.0.19045.5854
Windows 11 22h2Operating system
Affected:< 10.0.22621.5335
Windows 11 23h2Operating system
Affected:< 10.0.22631.5335
Windows 11 24h2Operating system
Affected:< 10.0.26100.4061

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 installed Windows build version
    Run 'winver' or 'systeminfo | findstr /C:"Build"' from command prompt to obtain the OS build number
    Affected if The build number falls below the fixed version for your Windows release (e.g., below 10.0.19045.5854 for Windows 10 22h2)
  2. Confirm Windows Installer service status
    Open Services (services.msc) or run 'sc query msiserver' to verify the Windows Installer service exists and is configurable
    Affected if The Windows Installer service (msiserver) is present and operational on the system
  3. Verify Windows Update patch installation
    Open Settings > Windows Update > Update history, or run 'powershell Get-HotFix | Where-Object {$_.Description -like "Security Update"}' to list installed security updates
    Affected if No security update corresponding to CVE-2025-29837 appears in the installed updates history

You are affected if your Windows build version is lower than the fixed threshold for your specific Windows release and the Windows Installer component is in use.

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.21014 / 10.0.14393.8066 / 10.0.17763.7314 or later
Fixed in 10.0.10240.2101410.0.14393.806610.0.17763.7314
Interim mitigation

Apply the Microsoft security update for CVE-2025-29837 through Windows Update or manual patch deployment to resolve the improper link resolution in Windows Installer.

Recommended fix High confidence

March 2025 Windows Security Update (KB5002537 or subsequent cumulative update) - specific build numbers vary by Windows version: Win10 1507: 10.0.10240.21014, Win10 1607: 10.0.14393.8066, Win10 1809: 10.0.17763.7314, Win10 21h2: 10.0.19044.5854, Win10 22h2: 10.0.19045.5854, Win11 22h2: 10.0.22621.53

  1. Open Settings > Windows Update and check for updates
  2. Install all pending Windows security updates, particularly the March 2025 security update for Windows Installer
  3. Alternatively, download the specific security update from the Microsoft Update Catalog matching your Windows version (KB5002537 or subsequent cumulative update)
  4. Restart the system after updates are installed
  5. Verify the installed build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows update risks apply - updates should be tested in non-production environments first; enterprise deployments may require controlled rollout

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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