dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 1 Jul 2025.
Windows 10 1507Operating system · Microsoft

CVE-2025-33053

HIGH · 8.8 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 10.0.10240.21034 / 10.0.14393.8148 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable 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
External control of file name or path in Internet Shortcut Files allows an unauthorized attacker to execute code over a network.

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 path traversal/injection vulnerability in how Windows processes Internet Shortcut Files (.url). An attacker can craft a malicious .url file that controls the file path or name, allowing arbitrary code execution when the victim opens or processes the shortcut file. The 'over a network' aspect suggests the malicious shortcut could point to remote malicious resources.

MitigationApply vendor security updates for affected Windows versions immediately. Until patched, disable automatic processing of .url files and warn users not to open shortcut files from untrusted sources.

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.21034
Windows 10 1607Operating system
Affected:< 10.0.14393.8148
Windows 10 1809Operating system
Affected:< 10.0.17763.7434
Windows 10 21h2Operating system
Affected:< 10.0.19044.5965
Windows 10 22h2Operating system
Affected:< 10.0.19045.5965
Windows 11 22h2Operating system
Affected:< 10.0.22621.5472
Windows 11 23h2Operating system
Affected:< 10.0.22631.5472
Windows 11 24h2Operating system
Affected:< 10.0.26100.4270

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

CVSS:3.1/AV:N/AC:L/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 installed Windows version
    Open Settings > System > About, or run 'winver' command, or run 'systeminfo' in Command Prompt and look at the OS Version / Build number
    Affected if The build number is lower than the thresholds listed: 10240.21034 (1507), 14393.8148 (1607), 17763.7434 (1809), 19044.5965 (21h2), 19045.5965 (22h2), 22621.5472 (22h2), 22631.5472 (23h2), 26100.4270 (24h2)
  2. Confirm Windows edition
    Run 'winver' or check Settings > System > About to verify if the system is Windows 10 1507, 1607, 1809, 21h2, 22h2 or Windows 11 22h2, 23h2, or 24h2
    Affected if The Windows edition matches one of the affected versions listed and the build number is below the corresponding threshold

A system is affected if it runs any of the listed Windows 10 or Windows 11 versions with a build number lower than the specified threshold for that version.

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.21034 / 10.0.14393.8148 / 10.0.17763.7434 or later
Fixed in 10.0.10240.2103410.0.14393.814810.0.17763.7434
Interim mitigation

Apply vendor security updates for affected Windows versions immediately. Until patched, disable automatic processing of .url files and warn users not to open shortcut files from untrusted sources.

Recommended fix High confidence

Windows 10 1507 to build 10.0.10240.21034 | Windows 10 1607 to build 10.0.14393.8148 | Windows 10 1809 to build 10.0.17763.7434 | Windows 10 21h2 to build 10.0.19044.5965 | Windows 10 22h2 to build 10.0.19045.5965 | Windows 11 22h2 to build 10.0.22621.5472 | Windows 11 23h2 to build 10.0.22631.5472

  1. Check current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Identify which Windows 10 or 11 version and build is installed from the list of affected versions
  3. Apply Windows updates via Settings > Update & Security > Windows Update, or manually download and install the appropriate cumulative update for your version
  4. Alternatively, use Windows Server Update Services (WSUS) or Microsoft Update Catalog to deploy the security update
  5. Restart the system after applying the update
  6. Verify the fix by checking the installed build matches or exceeds: 10.0.10240.21034 (Win10 1507), 10.0.14393.8148 (Win10 1607), 10.0.17763.7434 (Win10 1809), 10.0.19044.5965 (Win10 21h2), 10.0.19045.5965 (Win10 22h2), 10.0.22621.5472 (Win11 22h2), 10.0.22631.5472 (Win11 23h2), or 10.0.26100.4270 (Win11 24h2)
Caveat Standard Windows update risks apply (potential compatibility issues with legacy software; test updates in staging environment before broad deployment)

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

Fix this in Windows 10 1507 Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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