dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-57084

MEDIUM · 5.5 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 →
58/100
Remediation priority · Elevated
No privileges 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 of uninitialized resource in Windows File Explorer allows an unauthorized attacker to disclose information 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 use-of-uninitialized-resource vulnerability in Windows File Explorer enables a local unauthenticated attacker to potentially read sensitive information from uninitialized memory regions. This is an information-disclosure flaw with local attack vector, requiring no special privileges to exploit.

MitigationApply the relevant Microsoft security update for Windows File Explorer through Windows Update or enterprise patch management. Validate File Explorer functionality post-patch in testing environments before broad deployment.

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 2012Operating system
Affected:all versions= r2

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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 major version and build number
    Open Command Prompt or PowerShell and run 'winver' to display the Windows version and build, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' for detailed system information
    Affected if The build number falls below any of the threshold values for your Windows edition (10.0.14393.9339 for 1607, 10.0.17763.9020 for 1809, 10.0.19044.7548 for 21h2, 10.0.19045.7548 for 22h2, 10.0.26100.8875 for 11 24h2, 10.0.26200.8875 for 11 25h2, 10.0.28000.2269 for 11 26h1) or is any version of Windo
  2. Identify exact Windows build via registry
    Run 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild' and '/v DisplayVersion' (if applicable) to retrieve the precise build number
    Affected if The CurrentBuild value is numerically lower than the threshold corresponding to your Windows release (1607, 1809, 21h2, 22h2, 11 24h2, 25h2, or 26h1)
  3. Confirm Windows edition and release
    Run 'winver' or check system properties to determine if the system is Windows 10 1607, 1809, 21h2, 22h2, Windows 11 24h2/25h2/26h1, or Windows Server 2012/2012 R2
    Affected if The system runs any version of Windows Server 2012 or Windows Server 2012 R2 (all versions affected), or a Windows 10/11 version with a build number below the respective threshold
  4. Verify File Explorer is in use
    Confirm File Explorer (explorer.exe) is present and functional on the system; the vulnerability exists within the File Explorer component itself
    Affected if File Explorer is accessible to the local user (this is true for all standard Windows installations, as the vulnerability requires only local access with no special privileges)

A system is affected if it runs Windows 10 version 1607 through 22h2, Windows 11 24h2/25h2/26h1, or any version of Windows Server 2012/2012 R2 with a build number below the specified thresholds for the respective 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 the relevant Microsoft security update for Windows File Explorer through Windows Update or enterprise patch management. Validate File Explorer functionality post-patch in testing environments before broad deployment.

Recommended fix High confidence

Windows 10/11 monthly security updates containing the CVE-2026-57084 fix (builds listed above); Windows Server 2012/R2 users must migrate to supported Windows Server version (e.g., Windows Server 2019/2022)

  1. Check the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Identify which Windows 10 or 11 version/build is currently installed
  3. For Windows 10 1607 systems: Upgrade to build 10.0.14393.9339 or later via Windows Update or Microsoft Update Catalog
  4. For Windows 10 1809 systems: Upgrade to build 10.0.17763.9020 or later via Windows Update
  5. For Windows 10 21h2 systems: Upgrade to build 10.0.19044.7548 or later
  6. For Windows 10 22h2 systems: Upgrade to build 10.0.19045.7548 or later
  7. For Windows 11 24h2 systems: Upgrade to build 10.0.26100.8875 or later
  8. For Windows 11 25h2 systems: Upgrade to build 10.0.26200.8875 or later
Caveat Windows Server 2012/R2 has no patch available - migration to newer OS required; ensure application compatibility before upgrading Windows 10/11 systems

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,340
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,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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