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-111134 Overview
CVE-2026-111134 is a heap out-of-bounds read vulnerability in libfwsi, a library for parsing Windows Shell Item data. The flaw resides in the libfwsi_mtp_file_entry_values_read_data() function and affects all versions of the library through 20260522. Attackers can craft a Media Transfer Protocol (MTP) file entry shell item between 10 and 73 bytes with an item data size of 44 or more. Embedding this shell item in .lnk files, jump lists, or shell bags causes consumers of libfwsi to read past heap buffer bounds. The condition is tracked under CWE-125 and typically results in a crash of the parsing process.
Critical Impact
Crafted shell items trigger heap out-of-bounds reads in forensic and shell parsing tools that consume libfwsi, resulting in denial of service or potential disclosure of adjacent heap memory.
Affected Products
- libfwsi library maintained by the libyal project
- All releases through version 20260522
- Downstream forensic and shell-item parsers that embed libfwsi (consumers processing .lnk files, jump lists, or shell bags)
Discovery Timeline
- 2026-10-15 - CVE-2026-111134 published to the National Vulnerability Database (NVD)
- 2026-10-16 - Last updated in NVD database
Technical Details for CVE-2026-111134
Vulnerability Analysis
The vulnerability resides in libfwsi_mtp_file_entry_values_read_data(), which parses MTP file entry shell item values. The function reads a declared item data size field from the shell item but does not sufficiently validate the declared size against the actual buffer length provided to the parser. When an attacker supplies a shell item of only 10 to 73 bytes but declares an item data size of 44 or more, the function proceeds to read fields past the end of the supplied heap buffer. The result is a heap out-of-bounds read classified under CWE-125. Because libfwsi is embedded in forensic triage tools, shell artifact parsers, and digital investigation suites, a malicious artifact can crash the consumer or leak uninitialized adjacent heap memory into log output.
Root Cause
The root cause is missing bounds enforcement between the declared item_data_size field inside the MTP shell item structure and the actual size of the heap buffer passed to the parser. The relevant parsing path in libfwsi_mtp_file_entry_values.c lines 245-267 advances offsets based on attacker-controlled values before verifying that the remaining buffer length is sufficient.
Attack Vector
Exploitation requires local user interaction. An attacker delivers a malicious .lnk file, jump list, or shell bag containing a crafted MTP file entry shell item. When a forensic analyst, DFIR tool, or shell parsing utility processes the artifact, libfwsi triggers the out-of-bounds read. The attack vector is particularly relevant to incident response workflows that ingest attacker-supplied artifacts for analysis. Refer to the VulnCheck advisory for CVE-2026-111134 and the HackMD technical analysis for a step-by-step breakdown of the parser state when the invalid read occurs.
Detection Methods for CVE-2026-111134
Indicators of Compromise
- .lnk files, automaticDestinations-ms jump lists, or shell bag registry hives containing MTP file entry shell items with a total size between 10 and 73 bytes.
- Shell items where the embedded item_data_size field declares 44 bytes or more while the containing shell item is shorter than that value.
- Unexpected crashes or AddressSanitizer heap-buffer-overflow reports from forensic tools during artifact ingestion.
Detection Strategies
- Scan artifact collections for shell items whose declared data size exceeds the enclosing shell item length before parsing.
- Run libfwsi consumers under AddressSanitizer or Valgrind during triage of untrusted artifacts to surface the out-of-bounds read.
- Compare file sizes of inbound .lnk and jump list artifacts against expected ranges, and quarantine anomalously short shell items that reference MTP class identifiers.
Monitoring Recommendations
- Alert on repeated crashes of forensic parsing processes consuming shell artifacts from a single evidence source.
- Log and review ingestion failures in DFIR pipelines, correlating with the source of the submitted artifact.
- Monitor forensic workstations for unexpected process terminations of tools linked against libfwsi.
How to Mitigate CVE-2026-111134
Immediate Actions Required
- Inventory all forensic and shell-parsing tooling that statically or dynamically links against libfwsi and record installed versions.
- Isolate artifact triage workflows on dedicated workstations or sandboxes so a parser crash does not disrupt broader investigation infrastructure.
- Validate inbound .lnk files, jump lists, and shell bag hives for malformed MTP shell items before loading them into analysis tools.
Patch Information
At the time of publication, the libfwsi GitHub repository is the authoritative source for fixes. Users should track upstream commits beyond version 20260522 and rebuild downstream consumers against a patched version once the maintainers release a corrected libfwsi_mtp_file_entry_values_read_data() implementation that validates item_data_size against the remaining buffer length.
Workarounds
- Reject or pre-filter shell items whose declared data size exceeds the enclosing shell item length during artifact intake.
- Run libfwsi-based parsers inside a container, VM, or restricted process so a crash or memory read does not affect the host.
- Limit processing of untrusted .lnk, jump list, and shell bag artifacts to isolated analyst machines until a patched release is available.
# Configuration example
# Verify installed libfwsi version against vulnerable baseline
ldconfig -p | grep libfwsi
strings $(ldconfig -p | awk '/libfwsi/ {print $NF; exit}') | grep -i '20260522'
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

