Is CVE-2026-111133 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-111133 being exploited in the wild.

How severe is CVE-2026-111133?

Medium severity, with a CVSS score of 6.1, published 15 October 2026.

Which products and versions are affected?

Libyal Fsapfstools through 20260921; Libyal Libfsapfs through 20260921; Unknown dfVFS affected versions not specified; Unknown Plaso affected versions not specified; and 1 more.

Is there a fix for CVE-2026-111133?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-111133 attacked?

It is attacked over the network or with local access, in a software library.

Am I affected by CVE-2026-111133?

Check whether you run Libyal Fsapfstools, Libyal Libfsapfs, Unknown dfVFS or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-111133: libfsapfs integer underflow in libfsapfs_key_encrypted_key_read_data

CVE-2026-111133 · Severity: medium · CVSS 6.1 · Published 2026-10-15

libfsapfs is a library for reading Apple File System (APFS) volumes. An integer underflow vulnerability in encrypted key handling allows attackers to craft malicious APFS images that trigger heap out-of-bounds memory reads, potentially exposing sensitive data or crashing forensic and analysis tools before password verification occurs.

Vendors: Libyal, Unknown.

Quick answers

Is CVE-2026-111133 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-111133 being exploited in the wild.
How severe is CVE-2026-111133?: Medium severity, with a CVSS score of 6.1, published 15 October 2026.
Which products and versions are affected?: Libyal Fsapfstools through 20260921; Libyal Libfsapfs through 20260921; Unknown dfVFS affected versions not specified; Unknown Plaso affected versions not specified; and 1 more.
Is there a fix for CVE-2026-111133?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-111133 attacked?: It is attacked over the network or with local access, in a software library.
Am I affected by CVE-2026-111133?: Check whether you run Libyal Fsapfstools, Libyal Libfsapfs, Unknown dfVFS or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is an integer underflow in the libfsapfs_key_encrypted_key_read_data() function triggered by crafted HMAC or wrapped KEK (Key Encryption Key) attribute lengths in encrypted APFS images. Attackers can supply malformed encrypted volumes that crash applications like fsapfsinfo, pyfsapfs, dfVFS, and plaso, or read adjacent heap memory—with the critical flaw that this occurs before password checks are performed. A fix exists for versions after 20260921.

Affected products

libyal libfsapfs through 20260921
libyal fsapfstools through 20260921
<UNKNOWN> pyfsapfs affected versions not specified
<UNKNOWN> dfVFS affected versions not specified
<UNKNOWN> plaso affected versions not specified

Timeline

2026-10-15: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.