Eclipse ThreadX - NetX Duo: Incomplete Cleanup
CVE-2026-11576 is a high-severity incomplete cleanup vulnerability in Eclipse ThreadX - NetX Duo from Eclipse Foundation, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected Eclipse ThreadX - NetX Duo versions: 6.4.2 through 6.5.0.202601. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.46% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Eclipse ThreadX - NetX Duo you run against the affected versions below, and install the vendor's latest release.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Eclipse Foundation | Eclipse ThreadX - NetX Duo | 6.4.2 through 6.5.0.202601 | Not stated |
| Eclipse | Threadx Netx Duo | 6.4.2 through 6.5.0.202601 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by CNA (eclipse.org).
Official description
The security fix for CVE-2025-0728 in eclipse-threadx NetX Duo refactors error handling in the HTTP server PUT process to use a shared cleanup label, but this unified cleanup path unconditionally calls fx_file_close() even when the file was never successfully opened. Multiple error branches jump to the shared cleanup label before any file open operation has occurred, causing fx_file_close() to operate on an uninitialized file handle, leading to undefined behavior, double-close issues, or memory corruption.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incomplete Cleanup
The product does not properly clean up and remove temporary or supporting resources after they have been used.
How developers prevent this class of flaw
- Temporary files and other supporting resources should be deleted/released immediately after they are no longer needed.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
Other vulnerabilities in Eclipse ThreadX - NetX Duo
- 8.7 High severity
- 8.8 High severity
- 9.3 Critical severity
- 8.7 High severity
- 8.7 High severity
- 8.7 High severity
Recent Incomplete Cleanup vulnerabilities
- 7.5 High severity
- 9.6 Critical severity
- 8.1 High severity
- 9.8 Critical severity
- 7.5 High severity
- 8.2 High severity
Spotted an error? Tell us.