Quick answers
- Is CVE-2026-92449 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92449 being exploited in the wild.
- How severe is CVE-2026-92449?
- Informational severity, published 20 October 2026.
- Which products and versions are affected?
- Eclipse ThreadX GUIX 6.3.0 through 6.5.1.202602a.
- Is there a fix for CVE-2026-92449?
- Yes: fixed in GUIX 6.5.2.202603. Until then: Load binary resource theme files only from trusted sources. There is no build configuration option to disable the theme loader while keeping the rest of the binary resource API available. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-92449 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-92449?
- Check whether you run Eclipse ThreadX GUIX 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.
How to fix
- Fixed in: GUIX 6.5.2.202603
Load binary resource theme files only from trusted sources. There is no build configuration option to disable the theme loader while keeping the rest of the binary resource API available.
Technical details
The `_gx_binres_pixelmap_table_load()` function indexes a pixelmap table using an unbounded value from the theme file without validating it against the table size, resulting in a heap out-of-bounds write in GUIX-allocated memory. An attacker can craft a theme resource with a large pixelmap index to trigger writes of up to 256 KB of zeros followed by an uninitialized pointer, with the capability disabled only if binary resource support is explicitly removed from the build. No arbitrary code execution was demonstrated.
Affected products
- Eclipse ThreadX GUIX 6.3.0 through 6.5.1.202602a
Timeline
- 2026-10-02: disclosed
- 2026-10: patched: GUIX 6.5.2.202603 released
- 2026-10-20: advisory