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-91189 Overview
CVE-2026-91189 is an integer overflow vulnerability [CWE-190] in the Eclipse ThreadX GUIX binary resource loader. The loader fails to validate that a font page's glyph range is well formed before allocating memory. Attackers craft a malicious binary resource file in which gx_page_header_first_glyph exceeds gx_page_header_last_glyph, causing the glyph count calculation to underflow. The subsequent multiplication wraps to a small value, producing an undersized heap buffer that the loader then overwrites with attacker-controlled glyph records.
Critical Impact
Successful exploitation yields heap memory corruption in the context of the GUIX-based application, enabling arbitrary code execution with high confidentiality, integrity, and availability impact on the local target.
Affected Products
- Eclipse ThreadX GUIX (binary resource loader)
- Embedded applications using GUIX for graphical user interfaces
- Devices parsing untrusted GUIX binary resource files
Discovery Timeline
- 2026-10-20 - CVE CVE-2026-91189 published to NVD
- 2026-10-20 - Last updated in NVD database
Technical Details for CVE-2026-91189
Vulnerability Analysis
The flaw resides in GUIX's binary resource loader, which parses font page headers from file-provided data. The header fields gx_page_header_first_glyph and gx_page_header_last_glyph are read verbatim from the input file. The loader only validates the upper bound of last_glyph and never confirms that first_glyph <= last_glyph.
When an attacker supplies a page header where first_glyph > last_glyph, the expression last - first + 1 underflows in unsigned arithmetic. The result is a very large glyph count value. The loader multiplies this count by the per-glyph record size to size an allocation buffer, and this multiplication is also unchecked.
The product wraps a second time and produces a small allocation size. The loader then enters its load pass, recomputes the count in a narrower integer type, and writes attacker-controlled glyph records into the undersized heap buffer. The resulting out-of-bounds write corrupts adjacent heap metadata and allows arbitrary code execution within the GUIX application process.
Root Cause
The root cause is missing input validation combined with unchecked integer arithmetic on untrusted file data. Neither the range relationship between first_glyph and last_glyph nor the count-times-size multiplication is guarded against overflow or underflow before allocation.
Attack Vector
Attack requires local delivery of a crafted GUIX binary resource file and user interaction to load it. The affected application must parse the attacker-supplied resource through the vulnerable loader path. See the GitHub Security Advisory GHSA-hgcj-22cg-4hfv for additional technical details.
Detection Methods for CVE-2026-91189
Indicators of Compromise
- GUIX binary resource files whose font page headers contain first_glyph values greater than last_glyph.
- Unexpected heap corruption, crashes, or control-flow deviations in processes that load GUIX resource bundles.
- Delivery of GUIX .gxb or equivalent binary resource files from untrusted sources, email attachments, or removable media.
Detection Strategies
- Add a static parser that enumerates font pages in GUIX binary resources and flags headers where first_glyph > last_glyph or where (last - first + 1) * record_size overflows.
- Monitor process telemetry for GUIX-based applications exhibiting heap corruption signatures, aborts, or unexpected child process creation after resource load.
- Hunt build artifacts and firmware images for GUIX resource files that fail schema validation against expected glyph ranges.
Monitoring Recommendations
- Track file-system and USB events delivering GUIX resource files to engineering workstations and embedded devices.
- Alert on crashes or watchdog resets correlated with GUIX resource load operations on production devices.
- Record build-pipeline validation failures for third-party font and resource bundles before firmware signing.
How to Mitigate CVE-2026-91189
Immediate Actions Required
- Update Eclipse ThreadX GUIX to the fixed version referenced in the GHSA-hgcj-22cg-4hfv advisory.
- Restrict loading of GUIX binary resources to signed, trusted bundles produced in-house.
- Audit distributed firmware images for vulnerable GUIX versions and schedule patched builds.
Patch Information
Refer to the upstream Eclipse ThreadX GUIX repository and the GitHub Security Advisory for patched commits and release notes. Apply the fix that adds explicit validation of the glyph range ordering and performs checked multiplication before buffer allocation.
Workarounds
- Validate GUIX binary resource files out-of-band before loading, rejecting any font page where first_glyph > last_glyph.
- Disable or avoid dynamic loading of GUIX resources from user-controlled storage until the patch is deployed.
- Enforce code-signing and integrity checks on all resource bundles delivered to embedded targets.
# Configuration example: pre-load validation pseudocode
# Reject any GUIX resource whose font page header violates range ordering
validate_guix_resource() {
file="$1"
python3 ./check_guix_glyph_ranges.py "$file" || {
echo "REJECT: $file failed glyph range validation"
return 1
}
}
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

