CVE-2026-114408
NULL pointer dereference in ICMPv6 Packet Too Big processing when the destination table is full
In Eclipse ThreadX NetX Duo versions 6.4.5.202504 through 6.5.2.202603a, built with IPv6 path MTU discovery, the ICMPv6 Packet Too Big handler uses the destination-table entry it adds without checking that the add succeeded. A sender on the network can fill the destination table with Packet Too Big messages quoting new destinations, after which the next message makes the IP helper thread dereference a NULL pointer, crashing it on targets that fault on address 0 and stopping all network processing.
Fixes and workarounds
Fix
NetX Duo (eclipse threadx): GitHub reports patched versions 6.5.2.202603b. Check the advisory for the affected release branch.
Source: GitHub GHSA-xjgr-2wmf-f78jAffected products and versions
| Product | Versions | Authority |
|---|---|---|
| Eclipse ThreadX Eclipse Foundation |
≥ 6.4.5; ≤ 6.5.2.202603a (affected, custom)
Other versions: unaffected |
CNA: eclipse |
NetX DuoNetX Duo
eclipse threadx |
>= 6.4.5.202504, <= 6.5.2.202603a (affected, GitHub advisory range) | GitHub GHSA-xjgr-2wmf-f78j |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 4.0 / 8.7 high |
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N | CNA: eclipse |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://github.com/eclipse-threadx/netxduo/security/advisories/GHSA-xjgr-2wmf-f78jCNA: eclipse
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/482CNA: eclipse
- https://github.com/eclipse-threadx/netxduo/security/advisories/GHSA-xjgr-2wmf-f78jGitHub Security Advisories · advisory
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.