dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-49740

HIGH · 8.8 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 →
95/100
Remediation priority · Urgent
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
Protection mechanism failure in Windows SmartScreen allows an unauthorized attacker to bypass a security feature 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

Windows SmartScreen contains a protection mechanism failure that allows an unauthorized attacker to bypass a security feature over a network. This enables attackers to potentially execute malicious content or bypass integrity checks that SmartScreen normally provides.

MitigationApply Microsoft security updates for Windows when available. Monitor Microsoft's security advisories for CVE-2025-49740 for specific patch information and remediation guidance.

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
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 Windows build number
    Open PowerShell and run: winver OR run 'systeminfo' and look at OS Version / Build number. Alternatively, run 'winmgmt /ver' or check Registry: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion
    Affected if The installed build number is lower than any of these: 10240.21073 (Win10 1507), 14393.8246 (Win10 1607), 17763.7558 (Win10 1809), 19044.6093 (Win10 21h2/22h2), 22621.5624 (Win11 22h2), 22631.5624 (Win11 23h2), 26100.4652 (Win11 24h2)
  2. Verify SmartScreen is enabled
    Open Windows Security > App & browser control > Reputation-based protection settings, or run in PowerShell: Get-MpComputerStatus | Select-Object SmartScreenEnabled
    Affected if SmartScreen is disabled (SmartScreenEnabled shows False or settings are turned off)
  3. Confirm SmartScreen service status
    Run in PowerShell: Get-Service -Name SmartScreen | Select-Object Name, Status, StartType
    Affected if The SmartScreen service is not running or is set to Disabled

You are affected if your Windows build number falls below the thresholds listed AND SmartScreen is currently enabled in your environment.

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 when available. Monitor Microsoft's security advisories for CVE-2025-49740 for specific patch information and remediation guidance.

Recommended fix Moderate confidence

Install the Windows security update for CVE-2025-49740 from Microsoft Update (KB reference available at msrc.microsoft.com)

  1. Check current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Open Windows Update (Settings > Update & Security > Windows Update)
  3. Click 'Check for updates' and install all available security updates
  4. Restart the system when prompted to complete the installation
  5. After restart, verify the build number matches or exceeds the fixed version for your Windows release (Windows 10 1507: 10.0.10240.21073, 1607: 10.0.14393.8246, 1809: 10.0.17763.7558, 21h2: 10.0.19044.6093, 22h2: 10.0.19045.6093; Windows 11 22h2: 10.0.22621.5624, 23h2: 10.0.22631.5624, 24h2: 10.0.26100.4652)
  6. Alternatively, download and install the specific security update from Microsoft Update Catalog using the KB number provided in the MSRC advisory for CVE-2025-49740
Caveat None expected; this is a routine security patch for Windows SmartScreen protection mechanism

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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