dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-48816

HIGH · 7.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 →
80/100
Remediation priority · High
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
Integer overflow or wraparound in HID class driver allows an authorized attacker to elevate privileges 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

Integer overflow vulnerability in the HID (Human Interface Device) class driver allows a local authorized attacker to corrupt memory and elevate privileges to a higher integrity level. The flaw occurs when the driver mishandles certain HID report processing operations, causing integer wraparound that leads to buffer overflow conditions exploitable for privilege escalation.

MitigationApply the vendor-provided security update for the affected HID class driver. As a defensive measure, restrict unauthorized access to HID device interfaces and monitor for suspicious HID device connections in sensitive environments.

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
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 build number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the full build number (e.g., 10.0.19045.6093)
    Affected if The displayed build number falls below any of the following thresholds: 10240.21073 (Win10 1507), 14393.8246 (Win10 1607), 17763.7558 (Win10 1809), 19044.6093 (Win10 21h2), 19045.6093 (Win10 22h2), 22621.5624 (Win11 22h2), 22631.5624 (Win11 23h2), or 26100.4652 (Win11 24h2)
  2. Verify Windows release version family
    Run 'winver' to confirm whether the system is Windows 10 1507, 1607, 1809, 21h2, 22h2, or Windows 11 22h2, 23h2, or 24h2
    Affected if The system runs any of the listed Windows release versions and the build number is lower than the corresponding threshold from step 1
  3. Confirm presence of HID class driver
    Open Device Manager, expand 'Human Interface Devices', and verify that HID-compliant drivers are loaded and active. Alternatively, run 'sc query hidclass' in Command Prompt
    Affected if The HID class driver (hidclass.sys) is present and running, which is the default state on standard Windows installations

The environment is affected if the Windows build number is lower than the version-specific threshold for the detected Windows release, and the HID class driver is loaded (default state).

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 the vendor-provided security update for the affected HID class driver. As a defensive measure, restrict unauthorized access to HID device interfaces and monitor for suspicious HID device connections in sensitive environments.

Recommended fix High confidence

Apply the appropriate Windows Security Update (Cumulative) for your specific Windows version that includes the fix for CVE-2025-48816

  1. Open Settings > Update & Security > Windows Update and check for updates
  2. Install all available cumulative security updates for your Windows version
  3. Restart the system after applying updates
  4. Verify the installed update by running 'winver' to confirm the build number matches or exceeds the fixed version for your Windows release
Caveat Some older Windows 10 versions (1507, 1607, 1809) may be out of mainstream support; ensure compatibility with your organization's support lifecycle policy

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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