Quick answers
- Is CVE-2026-102760 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-102760 being exploited in the wild.
- How severe is CVE-2026-102760?
- Informational severity, published 29 September 2026.
- Which products and versions are affected?
- Eclipse ThreadX NetX Secure.
- Is there a fix for CVE-2026-102760?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-102760 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-102760?
- Check whether you run Eclipse ThreadX NetX Secure. 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.
Technical details
When NX_SECURE_KEY_CLEAR is enabled, NetX Secure attempts to wipe TLS records after handing them to the TCP layer. However, the TCP layer may have already released the packet back to the pool, causing the wipe operation to write zeros into freed or reused packets. When a reused packet's length no longer matches the original data, the wipe operation underflows and writes past the end of the packet pool, causing memory corruption.
Affected products
- Eclipse ThreadX NetX Secure
Timeline
- 2026-09-29: disclosed