CVE-2025-55086: Eclipse Foundation NextX Duo · CWE-1285
Affects Eclipse Foundation NextX DuoSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 6.4.4 when convenient.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.4.4
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade eclipse-threadx/netxduo to 6.4.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubeclipse-threadx/netxduopkg:github/eclipse-threadx/netxduoOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Upgrade affected devices and systems to NetXDuo version 6.4.4 or later once the patch is released by the Eclipse Foundation. 2. Implement network-level filtering to block or monitor suspicious DHCPv6 traffic, especially from untrusted sources, using firewalls or intrusion detection/prevention systems configured to inspect DHCPv6 packets. 3. Conduct an inventory of all devices running NetXDuo and assess their exposure to IPv6 networks with DHCPv6 enabled. 4. Where possible, disable DHCPv6 client functionality on devices that do not require it or restrict DHCPv6 server replies to trusted network segments. 5. Employ network segmentation to isolate vulnerable embedded devices from critical infrastructure and sensitive data networks. 6. Monitor device logs and network traffic for anomalies indicative of malformed DHCPv6 packets or memory errors. 7. Collaborate with device vendors and suppliers to ensure timely firmware updates and vulnerability disclosures. 8. Develop incident response plans specific to embedded device compromise or denial of service scenarios related to DHCPv6 vulnerabilities.
Description
In NetXDuo version before 6.4.4, a networking support module for Eclipse Foundation ThreadX, in the DHCPV6 client there was an unchecked index extracting the server DUID from the server reply. With a crafted packet, an attacker could cause an out of memory read.