CVE-2026-110598
Deferred Deferred - Pending Action

Integer Underflow in libyal libpff via Multi-Value Offsets

Vulnerability report for CVE-2026-110598, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-14

Last updated on: 2026-10-16

Assigner: VulnCheck

Description

Libyal libpff through 20260926 contains an integer underflow in libpff_record_entry_get_multi_value() that allows attackers to trigger heap out-of-bounds reads via non-monotonic multi-value offsets. Attackers can craft PST, OST or PAB files with decreasing PT_MV_STRING8, PT_MV_UNICODE or PT_MV_BINARY offsets to crash libpff, pypff or pffexport and expose adjacent heap memory.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-14
Last Modified
2026-10-16
Generated
2026-10-19
AI Q&A
2026-10-15
EPSS Evaluated
2026-10-18
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
libyal libpff 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-125 The product reads data past the end, or before the beginning, of the intended buffer.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-110598 is a heap out-of-bounds read vulnerability in the libpff library caused by an integer underflow in the multi-value property parser. It occurs when processing MAPI multi-valued string or binary properties in PST or OST files. The parser fails to validate that offsets in the property's offset array are monotonically increasing, allowing attackers to craft malicious files with decreasing offsets. This causes an unsigned integer underflow, leading to a wrapped size of approximately 4 GiB. When an application enumerates such a property, it triggers a heap out-of-bounds read, potentially crashing the application and exposing adjacent heap memory.

Detection Guidance

Detecting this vulnerability requires analyzing PST, OST, or PAB files for non-monotonic multi-value offsets. Use tools like libpff's pffinfo or pypff to parse files and check for crashes during processing. Enable AddressSanitizer or similar tools when compiling libpff to catch heap out-of-bounds reads during file parsing.

Impact Analysis

This vulnerability can impact users by causing applications like libpff, pypff, or pffexport to crash when processing maliciously crafted PST, OST, or PAB files. The crash may result in denial of service and potential exposure of adjacent heap memory, which could include sensitive data. While no out-of-bounds write or code execution has been established, the risk of information disclosure and service disruption remains a concern for affected systems.

Compliance Impact

This vulnerability primarily causes heap out-of-bounds reads and crashes in applications processing PST, OST, or PAB files. While it does not directly violate GDPR or HIPAA, it could lead to unauthorized data exposure if adjacent heap memory containing sensitive information is accessed during a crash. Denial of service through application crashes may also impact availability requirements in compliance frameworks.

Mitigation Strategies

Update libpff to the latest version that includes the monotonicity check for multi-value offsets. Avoid opening untrusted PST, OST, or PAB files until patched. Implement file validation before processing with libpff-based tools to reject malformed files.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-110598. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart