Quick answers
- Is CVE-2026-93475 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93475 being exploited in the wild.
- How severe is CVE-2026-93475?
- Informational severity, published 20 October 2026.
- Which products and versions are affected?
- Eclipse ThreadX NetX Secure <= 6.5.1.202602.
- Is there a fix for CVE-2026-93475?
- 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-93475 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-93475?
- Check whether you run Eclipse ThreadX NetX Secure 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 X.509 parser accepts RSA public keys of any size (up to 65535 bytes) but decrypts signatures into a fixed 512-byte buffer dimensioned for 4096-bit keys. The verification path fails to validate key size at multiple points: during parsing, during RSA initialization, and during the decryption operation. An attacker supplies an oversized key in their own certificate chain (checked before the trusted store), causing the modular exponentiation result to overflow the buffer and overwrite adjacent static variables.
Affected products
- Eclipse ThreadX NetX Secure <= 6.5.1.202602
Timeline
- 2026-10-20: disclosed
- 2026-10-02: patched: GHSA advisory published