{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-11576 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-11576 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-11576 is a high-severity memory corruption vulnerability in Eclipse ThreadX - NetX Duo, published on 19 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-11576 and fix it if it is affected.\n\nWhat it is: CVE-2026-11576 is a high-severity memory corruption vulnerability in Eclipse ThreadX - NetX Duo, published on 19 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-11576 in the wild and no public exploit code.\n\nAffected product: Eclipse ThreadX - NetX Duo. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-11576/ (Markdown: https://insights.sbomify.com/CVE-2026-11576/index.md)","id":"CVE-2026-11576","markdown":"https://insights.sbomify.com/CVE-2026-11576/index.md","name":"CVE-2026-11576","record":{"aliases":[],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Eclipse ThreadX RTOS","requires_auth":"none","summary":"A regression in Eclipse ThreadX NetX Duo causes memory corruption via double-close on uninitialized file handles during HTTP PUT error handling.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[{"product":"threadx_netx_duo","vendor":"eclipse"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-908","name":"Use of Uninitialized Resource"},{"id":"CWE-459","name":"Incomplete Cleanup"},{"id":"CWE-415","name":"Double Free"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Memory corruption in Eclipse ThreadX - NetX Duo","id":"CVE-2026-11576","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"The reported behavior does not constitute a privilege escalation.","id":"CVE-2026-11577"},"packages":[],"prev":{"headline":"PhonePe Payment Solutions \u003c 3.1.0 - Unauthenticated Payment Bypass via Forged Callback","id":"CVE-2026-11575"},"products":["Eclipse ThreadX - NetX Duo"],"published":"2026-06-19","related":[{"cvss_score":8.8,"headline":"Web http client: Unchecked Server-Side Malicious Packet Issue","id":"CVE-2025-55085","kev_date_added":null,"published":"2025-10-17"},{"cvss_score":8.7,"headline":"Denial of service in Eclipse ThreadX - NetX Duo","id":"CVE-2025-55102","kev_date_added":null,"published":"2026-01-27"},{"cvss_score":7.1,"headline":"Eclipse ThreadX NetX Duo HTTP component server denial of service","id":"CVE-2025-2260","kev_date_added":null,"published":"2025-04-06"},{"cvss_score":7.1,"headline":"Eclipse ThreadX NetX Duo HTTP server denial of service","id":"CVE-2025-0726","kev_date_added":null,"published":"2025-02-21"},{"cvss_score":7,"headline":"Integer wraparound, under-allocation, and heap buffer overflow in Eclipse ThreadX NetX Duo __portable_aligned_alloc()","id":"CVE-2024-2452","kev_date_added":null,"published":"2024-03-26"},{"cvss_score":6.9,"headline":"Potential out of bound read in _nx_ipv4_option_process()","id":"CVE-2025-55092","kev_date_added":null,"published":"2025-10-17"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-22","vendors":["Eclipse Foundation"]},"summary":"A regression in Eclipse ThreadX NetX Duo causes memory corruption via double-close on uninitialized file handles during HTTP PUT error handling.","url":"https://insights.sbomify.com/CVE-2026-11576/"}