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-111135 Overview
CVE-2026-111135 is a heap out-of-bounds read vulnerability in libfwsi through version 20260522. The flaw resides in the libfwsi_mtp_volume_values_read_data() function, which parses Media Transfer Protocol (MTP) volume shell items. Attackers can craft a 10 to 53 byte shell item with an item data size of 44 or more and embed it in a .lnk file, jump list, or shell bag. When a consuming process parses the malicious artifact, the function reads past the allocated heap buffer, causing a crash. The weakness is classified as [CWE-125 Out-of-Bounds Read].
Critical Impact
Crafted Windows shell items processed by libfwsi-based forensic or indexing tools can crash the consuming process, disrupting digital forensics and incident response workflows.
Affected Products
- libfwsi through version 20260522
- Forensic tooling that embeds libfwsi for parsing .lnk files, jump lists, and shell bags
- Downstream libyal-based utilities consuming MTP volume shell items
Discovery Timeline
- 2026-10-15 - CVE-2026-111135 published to the National Vulnerability Database
- 2026-10-21 - Last updated in NVD database
Technical Details for CVE-2026-111135
Vulnerability Analysis
The vulnerability occurs inside libfwsi_mtp_volume_values_read_data(), located in libfwsi/libfwsi_mtp_volume_values.c. The function parses MTP volume shell items without correctly validating the relationship between the declared item data size and the actual size of the heap-allocated input buffer. When a shell item is between 10 and 53 bytes but declares an item data size of 44 or greater, parsing continues beyond the buffer end. The result is a heap out-of-bounds read that terminates the consuming process. Technical analysis is available in the HackMD Out-of-Bounds Read Analysis and the VulnCheck Advisory for libfwsi.
Root Cause
The root cause is missing bounds enforcement between the attacker-controlled item_data_size field and the actual length of the heap buffer passed to the parser. The relevant source range is documented in the GitHub Source Code Snippet. Trust in the embedded size field without cross-checking the shell item length allows the read to overrun the allocation.
Attack Vector
An attacker crafts a shell item of 10 to 53 bytes with an item data size of 44 or more and embeds it in a Windows artifact such as a .lnk shortcut, jump list, or shell bag. When a user or automated pipeline parses the artifact with a libfwsi-based tool, the process reads beyond the buffer and crashes. The attack is local and requires user interaction to open or ingest the malicious file. Successful exploitation disrupts availability of the consuming process but does not grant code execution.
// No verified exploit code is published. See the HackMD and VulnCheck references
// for the parsing path and the crafted MTP volume shell item layout.
Detection Methods for CVE-2026-111135
Indicators of Compromise
- Unexpected crashes of forensic tools, indexers, or scripts that parse .lnk files, jump lists, or shell bags
- Presence of .lnk, automaticDestinations-ms, customDestinations-ms, or shell bag entries containing MTP volume shell items between 10 and 53 bytes with declared item data size of 44 or more
- Crash dumps referencing libfwsi_mtp_volume_values_read_data on the stack
Detection Strategies
- Add signature or YARA rules that flag MTP volume shell items whose declared item_data_size exceeds the containing shell item length
- Instrument forensic pipelines with AddressSanitizer or similar tooling to catch the out-of-bounds read during triage of untrusted artifacts
- Monitor process termination events for forensic utilities parsing user-supplied Windows shell artifacts
Monitoring Recommendations
- Log and alert on repeated abnormal exits of indexing services, DFIR tools, or batch parsers consuming shell items
- Track ingestion of .lnk, jump list, and shell bag files from untrusted sources into analysis environments
- Correlate crash telemetry with the hash of the triggering artifact to identify intentional denial-of-service attempts
How to Mitigate CVE-2026-111135
Immediate Actions Required
- Inventory tooling that embeds libfwsi and identify versions at or below 20260522
- Sandbox or isolate forensic parsing of untrusted .lnk files, jump lists, and shell bags
- Restrict ingestion of Windows shell artifacts from unverified sources until a patched build is deployed
Patch Information
No fixed version is referenced in the published advisory at the time of writing. Monitor the GitHub Repository for libfwsi and the VulnCheck Advisory for libfwsi for upstream commits that add bounds validation to libfwsi_mtp_volume_values_read_data().
Workarounds
- Run libfwsi-based parsers inside a container or restricted sandbox so crashes do not disrupt the host workflow
- Pre-filter shell items and drop MTP volume entries where declared item data size exceeds the containing shell item size
- Where feasible, apply a local patch that validates item_data_size against the actual buffer length before dereferencing
# Example triage wrapper: run parsing in an isolated process and recover from crashes
timeout 30s firejail --quiet --private \
parse_shellitems --input /mnt/evidence/suspect.lnk \
|| echo "libfwsi parser exited abnormally - review artifact for CVE-2026-111135 pattern"
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

