CVE-2026-132998

Description

A heap buffer overflow was found in libeot, a library that converts Embedded OpenType (EOT) fonts. Processing a specially crafted font file can cause the decompressor to write beyond the end of an allocated buffer, resulting in a crash or possible memory corruption.

Statement

Red Hat Enterprise Linux 8 and 9 include the libeot package, which contains this flaw. However, no Red Hat Enterprise Linux component uses the library: LibreOffice is built without EOT support and no other shipped package requires libeot. Red Hat Enterprise Linux 10 does not include libeot. The vulnerable code can only be reached by directly processing untrusted font files with the eot2ttf utility or with applications that link against libeot. The flaw is fixed in libeot 0.0.2.

Mitigation

There is currently no mitigation available for this issue.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score6.5N/AN/A
Attack VectorNetworkN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredNoneN/AN/A
User InteractionRequiredN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Red Hat CVSS v3 Score Explanation

Demonstrated impact when an affected consumer processes an attacker-supplied font: crash (availability). Write length is attacker-controlled; write-content control and code execution were not demonstrated. No Red Hat product ships an affected consumer (libeot unconsumed in RHEL 8/9, absent in RHEL 10).

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory; Execute Unauthorized Code or Commands

Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.

Other

Technical Impact: Unexpected State

Subsequent write operations can produce undefined or unexpected results.

Acknowledgements

Upstream acknowledges Clifford Ressel (Nori Agentic) as the original reporter.

Frequently Asked Questions

Want to get errata notifications? Sign up here.