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-111133 Overview
CVE-2026-111133 is an integer underflow vulnerability in libfsapfs through version 20260921. The flaw resides in the libfsapfs_key_encrypted_key_read_data() function and allows attackers to trigger heap out-of-bounds reads via crafted Key Encryption Key (KEK) attributes. An attacker supplies a malformed encrypted Apple File System (APFS) image containing malformed HMAC or wrapped KEK attribute lengths. Parsing the crafted image causes tools such as fsapfsinfo, pyfsapfs, dfVFS, or plaso to crash and read adjacent heap memory before password checks occur. The vulnerability is tracked under CWE-125 (Out-of-Bounds Read).
Critical Impact
Attackers can crash forensic parsing tooling and leak adjacent heap memory contents without authentication by supplying a malicious APFS image.
Affected Products
- libfsapfs through 20260921
- Downstream consumers including fsapfsinfo, pyfsapfs, dfVFS, and plaso
- Digital forensics workflows that ingest untrusted APFS disk images
Discovery Timeline
- 2026-10-15 - CVE-2026-111133 published to the National Vulnerability Database (NVD)
- 2026-10-16 - Last updated in NVD database
Technical Details for CVE-2026-111133
Vulnerability Analysis
The vulnerability stems from an integer underflow during KEK attribute parsing in libfsapfs_key_encrypted_key_read_data(). The function processes attribute lengths from an attacker-controlled APFS container without sufficient validation. When the parser subtracts a header size from an attribute length smaller than the header, the computation underflows into a large unsigned value. The parser then uses that large value as a read bound against the attribute buffer. This results in a heap out-of-bounds read that occurs before password checks execute. Technical analysis is documented in the HackMD write-up and the VulnCheck advisory.
Root Cause
The root cause is missing bounds validation on HMAC and wrapped KEK attribute length fields prior to arithmetic operations. The vulnerable code paths are visible in the libfsapfs_key_encrypted_key.c source and the adjacent parsing block. The parser trusts length fields from untrusted container metadata before subtracting fixed header sizes.
Attack Vector
Exploitation requires local access and user interaction. An attacker crafts a malicious APFS image with manipulated KEK attribute length fields. A victim then opens the image with a tool linked against libfsapfs, such as fsapfsinfo or a plaso ingestion pipeline. The parser dereferences memory outside the allocated attribute buffer, producing a crash and leaking adjacent heap bytes. The read occurs before password validation, so no credentials are required.
No verified public exploit code is available. Refer to the HackMD Analysis Post for the technical write-up of the parsing flow.
Detection Methods for CVE-2026-111133
Indicators of Compromise
- Unexpected crashes or SIGSEGV terminations of fsapfsinfo, pyfsapfs, dfVFS, or plaso processes during image ingestion
- APFS container images with KEK attribute length fields smaller than their declared header sizes
- Forensic job failures correlated with ingestion of externally sourced disk images
Detection Strategies
- Run forensic parsers under memory sanitizers such as AddressSanitizer during triage of untrusted images to surface out-of-bounds reads
- Monitor process termination telemetry on forensic workstations for abnormal exits of libyal-based tooling
- Hash and quarantine inbound APFS images, then compare parser behavior across patched and unpatched builds in an isolated environment
Monitoring Recommendations
- Log all invocations of fsapfsinfo and plaso pipelines along with input file hashes for post-incident review
- Alert on repeated parser crashes against the same image, which may indicate exploitation attempts
- Capture core dumps from forensic hosts to retain evidence of memory disclosure attempts
How to Mitigate CVE-2026-111133
Immediate Actions Required
- Inventory systems that embed libfsapfs, including plaso, dfVFS, and pyfsapfs deployments
- Restrict parsing of untrusted APFS images to isolated analysis virtual machines without access to sensitive data
- Require integrity verification of disk images before ingestion into shared forensic pipelines
Patch Information
Monitor the libfsapfs GitHub repository for a release that addresses the integer underflow in libfsapfs_key_encrypted_key_read_data(). Consult the VulnCheck Security Advisory for the current fix status. Rebuild and redistribute downstream packages such as plaso once a patched library is available.
Workarounds
- Avoid processing APFS images from untrusted sources until a fixed library version is deployed
- Execute forensic parsers inside sandboxed containers with restricted filesystem and network access
- Enable compiler hardening flags and run tooling under AddressSanitizer builds where feasible to turn out-of-bounds reads into controlled aborts
# Configuration example: run libfsapfs tooling inside an isolated container
docker run --rm --read-only --network=none \
-v "$(pwd)/images:/images:ro" \
forensics/libfsapfs:sanitized \
fsapfsinfo /images/suspect.dmg
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

