CVE-2025-0726
Eclipse Threadx Netx Duo ≤ 6.4.2
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2025-0726 is a high-severity Incomplete Cleanup (CWE-459) vulnerability in Eclipse Threadx Netx Duo. Its CVSS base score is 7.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked in the top 49% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-14 (Non-persistence) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-0726 affects the NetX HTTP server functionality in Eclipse ThreadX NetX Duo versions prior to 6.4.2. The vulnerability stems from a failure to close a file handle under certain error conditions, classified under CWE-459 (Incomplete Cleanup). This issue enables a denial-of-service condition, as evidenced by its CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), indicating high availability impact with no requirements for privileges or user interaction.
An unauthenticated attacker with network access can exploit this vulnerability by sending specially crafted packets, likely targeting PUT requests, to trigger the error condition. Once exploited, the server will return a 404 error for all subsequent file requests, effectively rendering the HTTP service unavailable and causing a denial of service.
Mitigation is available through upgrading to Eclipse ThreadX NetX Duo version 6.4.2 or later, as detailed in the project's GitHub security advisory (GHSA-pwf8-5q9w-m763) and the associated fix commit (c78d650be7377aae1a8704bc0ce5cc6f9f189014). As a workaround, users can disable PUT request support in the NetX HTTP server configuration.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-5084
Vulnerability Data
In NetX HTTP server functionality of Eclipse ThreadX NetX Duo before version 6.4.2, an attacker can cause a denial of service by specially crafted packets. The core issue is missing closing of a file in case of an error condition,…
more
resulting in the 404 error for each further file request. Users can work-around the issue by disabling the PUT request support.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.4.1
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover incomplete cleanup through dynamic analysis or resource-leak testing.
Non-persistence mechanisms explicitly initiate resources in a known state and terminate them, directly enforcing cleanup.
Session termination forces explicit release of session-related temporary resources.
Preventing unintended information transfer through shared resources requires complete cleanup of those resources.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure-development practices and coding standards normally require proper resource release and cleanup.
Life-cycle management encompasses disposal of temporary resources but does not specifically target runtime cleanup bugs.
Explicitly calls for removing sensitive data after use, directly addressing one class of incomplete cleanup.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Explicitly requires secure deletion of temporary or residual data, directly addressing incomplete cleanup.
SDLC practices include cleanup steps, yet the weakness can still occur if those steps are omitted.
Secure-coding rules can mandate explicit cleanup of temporary resources, but do not guarantee it.
Change-management processes may require cleanup verification, but the control itself does not address the weakness.