Quick answers
- Is CVE-2026-91057 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-91057 being exploited in the wild.
- How severe is CVE-2026-91057?
- Informational severity, published 20 October 2026.
- Which products and versions are affected?
- Eclipse ThreadX GUIX <= 6.5.1.202602a.
- Is there a fix for CVE-2026-91057?
- Yes: fixed in GUIX 6.5.2.202603. Until then: Set GX_STYLE_TEXT_COPY on the widget so GUIX copies text into its own NUL-terminated storage, or ensure application text passed to multi-line text views does not end with a lone carriage return.</anigation> <parameter name="timeline">[{"kind":"disclosed","at":"2026-10-02"},{"kind":"advisory","at":"2026-10-20"}] Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-91057 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-91057?
- 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
Set GX_STYLE_TEXT_COPY on the widget so GUIX copies text into its own NUL-terminated storage, or ensure application text passed to multi-line text views does not end with a lone carriage return.</anigation> <parameter name="timeline">[{"kind":"disclosed","at":"2026-10-02"},{"kind":"advisory","at":"2026-10-20"}]
Technical details
The `_gx_multi_line_text_view_display_info_get()` function in gx_multi_line_text_view_display_info_get.c performs an unchecked read of the byte following a carriage return to distinguish between `\r` and `\r\n` line terminators, without verifying that the byte remains within the GX_STRING's declared length. This out-of-bounds read can advance the caller's index past the string end, triggering a second out-of-bounds read in `_gx_multi_line_text_view_string_total_rows_compute()` if the adjacent byte is `0x0A`. Local, low-privilege code can trigger this via any multi-line text widget with text ending in carriage return; impact is memory read disclosure (single byte, not attacker-chosen) and potential denial of service on systems where the buffer sits at a memory boundary.
Affected products
- Eclipse ThreadX GUIX <= 6.5.1.202602a