CVE-2026-132999
Description
A use-after-free was found in libeot, a library that converts Embedded OpenType (EOT) fonts. Processing a specially crafted font file can cause the library to access memory after it has been freed, 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.4.
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 Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 6.5 | N/A | N/A |
| Attack Vector | Network | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | None | N/A | N/A |
| User Interaction | Required | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | None | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | High | N/A | N/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). The reported heap-address disclosure was not demonstrated, so no confidentiality impact is scored; write-content control and code execution were also 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
The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.
Confidentiality
Technical Impact: Read Memory
Read operations on freed memory can sometimes leak sensitive information instead of causing a crash
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.
Acknowledgements
Upstream acknowledges Clifford Ressel (Nori Agentic) as the original reporter.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.