Skip to main content
Vulnerability Database/CVE-2026-83565

CVE-2026-83565: Windows EFS Information Disclosure Flaw

CVE-2026-83565 is a buffer over-read vulnerability in Windows Encrypting File System that enables authorized attackers to access sensitive data locally. This article covers technical details, affected versions, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-83565 Overview

CVE-2026-83565 is a buffer over-read vulnerability in the Windows Encrypting File System (EFS). An authorized local attacker can trigger the flaw to read memory beyond an intended buffer boundary, resulting in information disclosure. The weakness is classified under [CWE-126] (Buffer Over-read).

The issue requires local access and low privileges, with no user interaction. Successful exploitation exposes sensitive in-process memory contents but does not affect integrity or availability. Microsoft published the advisory on October 13, 2026.

Critical Impact

An authenticated local user can disclose confidential information from EFS process memory, which may include cryptographic material or data from other users' encrypted workflows.

Affected Products

Discovery Timeline

  • 2026-10-13 - CVE CVE-2026-83565 published to NVD
  • 2026-10-13 - Last updated in NVD database

Technical Details for CVE-2026-83565

Vulnerability Analysis

The vulnerability resides in the Windows Encrypting File System, which transparently encrypts files on NTFS volumes. EFS handles cryptographic key material, file metadata, and user context in kernel and service memory during encryption and decryption operations.

A buffer over-read occurs when EFS reads past the end of an allocated buffer during request processing. The over-read returns adjacent memory to the caller, enabling an authorized local attacker to obtain data that should not be accessible. The impact is confined to confidentiality; the attacker cannot modify data or crash services through this flaw alone.

The [CWE-126] classification indicates the component uses a sequential read operation that fails to enforce the correct upper bound. See the Microsoft Security Update Guidance for component-specific technical details.

Root Cause

The root cause is insufficient bounds validation on a read operation inside an EFS code path. When a caller supplies crafted input, the component reads beyond the valid buffer length and returns the extra bytes. The flaw is a classic missing length-check pattern rather than a logic or cryptographic weakness.

Attack Vector

Exploitation requires local access and valid credentials on the target system. An attacker invokes EFS functionality through standard Windows interfaces with input crafted to trigger the over-read. The response or output surface returns leaked memory contents to the attacker's process.

The vulnerability is not exploitable remotely and no public proof-of-concept has been published. No exploitation in the wild has been reported, and the CVE is not listed in the CISA Known Exploited Vulnerabilities catalog.

No verified exploit code is available. Refer to the Microsoft Security Update Guidance for component and build-level technical references.

Detection Methods for CVE-2026-83565

Indicators of Compromise

  • No public indicators of compromise have been published for CVE-2026-83565.
  • Successful exploitation leaves minimal forensic artifacts because the operation is a memory read rather than a write or process spawn.

Detection Strategies

  • Monitor unusual process access patterns against EFS components (efsvc, lsass.exe EFS APIs) by non-administrative users.
  • Alert on repeated or scripted calls to EFS APIs from unexpected user contexts or newly created local accounts.
  • Correlate local authentication events with EFS activity to identify low-privilege accounts probing encryption subsystems.

Monitoring Recommendations

  • Enable Windows audit policies for object access and process creation on systems storing EFS-encrypted data.
  • Forward EFS-related event logs to a centralized SIEM for behavioral baselining of normal versus anomalous API usage.
  • Track installation status of the October 2026 Microsoft security updates across the fleet to confirm remediation coverage.

How to Mitigate CVE-2026-83565

Immediate Actions Required

  • Apply the Microsoft security update referenced in the Microsoft Security Update Guidance for CVE-2026-83565.
  • Restrict interactive and remote local logon rights to only required administrative and service accounts.
  • Audit local accounts on systems using EFS and remove unused or stale credentials.

Patch Information

Microsoft addressed CVE-2026-83565 in the October 2026 security update cycle. Administrators should install the applicable cumulative update for each supported Windows version as described in the Microsoft Security Update Guidance.

Workarounds

  • Limit use of EFS on multi-user systems where low-privilege accounts share hardware with sensitive encrypted data.
  • Enforce the principle of least privilege and remove unnecessary local logon rights to reduce the pool of potential attackers.
  • Apply application control policies to prevent execution of untrusted binaries by standard users on affected hosts.
bash
# Verify installation of the relevant Microsoft security update on Windows
wmic qfe list brief /format:table

# PowerShell: list installed hotfixes and filter by install date
Get-HotFix | Where-Object { $_.InstalledOn -ge '2026-10-13' } | Sort-Object InstalledOn

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.