dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-57091

HIGH · 7.8 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 10.0.14393.9339 / 10.0.17763.9020 or later.
See remediation →
80/100
Remediation priority · High
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
Stack-based buffer overflow in Windows File History Service allows an authorized attacker to elevate privileges locally.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 1mo 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 stack-based buffer overflow vulnerability exists in the Windows File History Service that allows a locally authorized attacker to execute arbitrary code with elevated privileges. The overflow occurs when the service processes input without proper bounds checking, enabling an attacker to overwrite stack memory and gain SYSTEM-level access.

MitigationApply Microsoft security patches for this vulnerability through Windows Update or enterprise patch management systems. Prioritize patching on systems where File History Service is enabled and users have local access.

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 1607Operating system
Affected:< 10.0.14393.9339
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
Windows Server 2016Operating system
Affected:< 10.0.14393.9339

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. Verify File History Service status
    Open Services console (services.msc) or run 'Get-Service FileHistoryService' in PowerShell to check if the File History Service is running or set to start automatically
    Affected if The service is running or set to Automatic start, as the vulnerability only applies when this service is enabled
  2. Confirm Windows version and build number
    Run 'winver' from Run dialog or execute 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' in Command Prompt to obtain the full version string
    Affected if The displayed version falls within the affected ranges: Windows 10 1607/1809/21h2/22h2, Windows 11 24h2/25h2/26h1, or Windows Server 2016 with build numbers below the fixed thresholds
  3. Extract precise build number for comparison
    Run 'winver' and note the Build number (e.g., 14393, 17763, 19044, 19045, 26100, 26200, 28000), or use PowerShell with '[Environment]::OSVersion.Version' to get the exact version object
    Affected if The build number is less than 14393.9339 (Windows 10 1607/Server 2016), 17763.9020 (Windows 10 1809), 19044.7548 (Windows 10 21h2), 19045.7548 (Windows 10 22h2), 26100.8875 (Windows 11 24h2), 26200.8875 (Windows 11 25h2), or 28000.2269 (Windows 11 26h1)
  4. Verify File History feature is configured
    Navigate to Settings > Update & Security > Backup > File History (or check registry key HKCU\Software\Microsoft\Windows\CurrentVersion\FileHistory for enabled status)
    Affected if File History backup feature has been configured or enabled on the system

The system is affected if the File History Service is running and the Windows build number is below the fixed version thresholds for the detected Windows release.

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.14393.9339 / 10.0.17763.9020 / 10.0.19044.7548 or later
Fixed in 10.0.14393.933910.0.17763.902010.0.19044.7548
Interim mitigation

Apply Microsoft security patches for this vulnerability through Windows Update or enterprise patch management systems. Prioritize patching on systems where File History Service is enabled and users have local access.

Recommended fix High confidence

Install the latest Windows security updates from Windows Update; the minimum fixed versions are listed in the version thresholds above (e.g., Windows 10 22h2 requires 10.0.19045.7548 or higher)

  1. Open Windows Settings and navigate to Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest security updates
  3. Alternatively, manually verify the installed version by running 'winver' command and confirm it meets or exceeds: Windows 10 1607: 10.0.14393.9339, 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.2269, Windows Server 2016: 10.0.14393.9339
  4. Restart the system after updates are installed
  5. Verify the File History service is running and monitor for any abnormal behavior
Caveat Standard Windows update apply with no special breaking changes expected for this security patch; ensure backups are verified before major system updates

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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