dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2026-49795

HIGH · 8.8 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 10.0.17763.9020 / 10.0.19044.7548 or later.
See remediation →
90/100
Remediation priority · Urgent
Zero-click 5 weeks old

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
Use after free in Windows Kernel allows an authorized attacker to elevate privileges locally.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 1w ago

Surfaced from public web coverage — external links open in a new tab.

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

A use-after-free vulnerability in the Windows Kernel enables a local authenticated attacker to exploit freed memory, potentially achieving arbitrary code execution with elevated (kernel-level) privileges. This memory corruption flaw allows privilege escalation from a standard user context to administrative or system-level access.

MitigationApply Microsoft security patches for this kernel vulnerability as soon as they become available; in the interim, minimize local attack surface by restricting physical access and limiting privileged local accounts.

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 1809Operating system
Affected:< 10.0.17763.9020
Windows 10 21h2Operating system
Affected:< 10.0.19044.7548
Windows 10 22h2Operating system
Affected:< 10.0.19045.7548
Windows 11 24h2Operating system
Affected:< 10.0.26100.8875
Windows 11 25h2Operating system
Affected:< 10.0.26200.8875
Windows 11 26h1Operating system
Affected:< 10.0.28000.2269< 10.0.28000.2525
Windows Server 2019Operating system
Affected:< 10.0.17763.9020
Windows Server 2022Operating system
Affected:< 10.0.20348.5386

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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
    Run `winver` from Start menu or execute `systeminfo` in Command Prompt and locate the 'OS Version' or 'Build' line
    Affected if The build number is lower than the fixed version for your specific Windows release (17763.9020 for 1809/Server 2019, 19044.7548 for 21h2, 19045.7548 for 22h2, 26100.8875 for 24h2, 26200.8875 for 25h2, 28000.2269/28000.2525 for 26h1, or 20348.5386 for Server 2022)
  2. Confirm Windows edition
    Run `winver` or check System Properties to identify whether you are running Windows 10, Windows 11, Windows Server 2019, or Windows Server 2022
    Affected if The edition matches any of the affected products listed in the CVE
  3. Verify current patch level
    Open Settings > Windows Update > Update History or run `powershell "(Get-HotFix | Sort-Object -Property InstalledOn -Descending)[0]"` to see the most recent installed security update
    Affected if No security updates have been installed after the CVE release date for your Windows version

You are affected if your Windows build number falls below the fixed threshold for your specific Windows edition and 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.17763.9020 / 10.0.19044.7548 / 10.0.19045.7548 or later
Fixed in 10.0.17763.902010.0.19044.754810.0.19045.7548
Interim mitigation

Apply Microsoft security patches for this kernel vulnerability as soon as they become available; in the interim, minimize local attack surface by restricting physical access and limiting privileged local accounts.

Recommended fix High confidence

Upgrade to the build version specified in the security update: Windows 10 1809 to 10.0.17763.9020, Windows 10 21h2 to 10.0.19044.7548, Windows 10 22h2 to 10.0.19045.7548, Windows 11 24h2 to 10.0.26100.8875, Windows 11 25h2 to 10.0.26200.8875, Windows 11 26h1 to 10.0.28000.2525, Windows Server 2019 t

  1. Identify the current Windows version and build number by running 'winver' or 'systeminfo'
  2. Determine which Windows 10 or Windows 11 version is installed (1809, 21h2, 22h2, 24h2, 25h2, or 26h1)
  3. For Windows Server 2019 or Windows Server 2022, note the current build number
  4. Apply the appropriate Windows Update or manually download and install the security update for the specific build version
  5. Verify the installation completed successfully by checking the new build version matches the fixed release: Windows 10 1809: 10.0.17763.9020, Windows 10 21h2: 10.0.19044.7548, Windows 10 22h2: 10.0.19045.7548, Windows 11 24h2: 10.0.26100.8875, Windows 11 25h2: 10.0.26200.8875, Windows 11 26h1: 10.0.28000.2525, Windows Server 2019: 10.0.17763.9020, Windows Server 2022: 10.0.20348.5386
Caveat Standard Windows cumulative update; review release notes for any known issues before deployment in production environments

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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