Quick answers
- Is CVE-2026-91186 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-91186 being exploited in the wild.
- How severe is CVE-2026-91186?
- Informational severity, published 20 October 2026.
- Which products and versions are affected?
- Eclipse ThreadX GUIX 6.5.1.202602a and earlier.
- Is there a fix for CVE-2026-91186?
- Yes: fixed in 6.5.2.202603. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-91186 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-91186?
- 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: 6.5.2.202603
Technical details
The PNG decoder does not validate chunk ordering and allows a duplicate IHDR chunk to be processed after IDAT. The second IHDR redefines image dimensions after the decode buffer has already been allocated based on the first header's dimensions. The unfilter pass then uses the new dimensions to iterate over the buffer, writing beyond its bounds via memmove with attacker-controlled extent. The vulnerability is reachable via the public API with a specially crafted PNG file and no user interaction required.
Affected products
- Eclipse ThreadX GUIX 6.5.1.202602a and earlier
Timeline
- 2026-10-02: disclosed
- 2026-10-20: advisory