Security advisory
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-102760
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 07:45 UTC · Revision 1
Source evidence
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.
osv:CVE-2026-102760
Complete source record
{
"id": "0ddb93cc1970dab8e1d1e62bcfe3556b08f32162e1c8f246747c92ed5610528b",
"url": "https://osv.dev/vulnerability/CVE-2026-102760",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "CVE-2026-102760",
"summary": "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.",
"evidence": "osv:CVE-2026-102760",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2026-102760",
"aliases": [
"CVE-2026-102760",
"GHSA-8w5x-ff58-2fr2"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "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"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/eclipse-threadx/netxduo",
"type": "GIT",
"events": [
{
"introduced": "009da2f05a9fc098b8d699b2b814e515631d41cb"
},
{
"last_affected": "1a0e9e43a03e37ddecfb6b49e9b078d6e1803d05"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "6.0"
},
{
"last_affected": "6.5.1.202602"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
}
]
}
}
],
"versions": [
"v6.4.1_rel",
"v6.5.1.202602_rel",
"v6.5.0.202601_rel",
"v6.4.5.202504_rel",
"v6.4.4.202503a",
"v.6.4.4.202503_rel",
"v6.4.3_rel",
"v6.4.2_rel",
"v6.4.0_rel",
"v6.3.0_rel",
"v6.2.1_rel",
"v6.2.0_rel",
"v6.1.12_rel",
"v6.1.11_rel",
"v6.1.10_rel",
"v6.1.9_rel",
"v6.1.8_rel",
"v6.1.7_rel",
"v6.1.6_rel",
"v6.1.5_rel",
"v6.1.4_rel",
"v6.1.3_rel",
"v6.1.2_rel",
"v6.1_rel",
"v6.0.2_rel",
"v6.0.1_rel",
"v6.0_rel"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-102760.json"
}
}
],
"modified": "2026-10-28T02:30:34.006747198Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/102xxx/CVE-2026-102760.json",
"https://github.com/eclipse-threadx/netxduo/security/advisories/GHSA-8w5x-ff58-2fr2",
"https://nvd.nist.gov/vuln/detail/CVE-2026-102760"
],
"provider_metadata": {
"cwe_ids": [
"CWE-416"
],
"cna_assigner": "eclipse",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/102xxx/CVE-2026-102760.json"
}
},
"related_cves": [
{
"value": "CVE-2026-102760",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 500938,
"published_at": "2026-09-29T17:29:11.787+00:00"
}