{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-102720 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-102720 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-102720 is a medium-severity memory corruption vulnerability in eclipse-threadx/netxduo, published on 29 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-102720 and fix it if it is affected.\n\nWhat it is: CVE-2026-102720 is a medium-severity memory corruption vulnerability in eclipse-threadx/netxduo, published on 29 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-102720 in the wild and no public exploit code.\n\nAffected product: eclipse-threadx/netxduo. 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-102720/ (Markdown: https://insights.sbomify.com/CVE-2026-102720/index.md)","id":"CVE-2026-102720","markdown":"https://insights.sbomify.com/CVE-2026-102720/index.md","name":"CVE-2026-102720","record":{"aliases":["GHSA-8hj5-p46x-5h28","GHSA-rw53-r2p7-qgmf"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"ThreadX NetX Duo","requires_auth":"none","summary":"A DHCP client flaw allows remote attackers to read memory past buffer boundaries via crafted DHCP offers, potentially disclosing sensitive data or causing crashes.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"A DHCP server, or anyone on the LAN who answers a DISCOVER first, can make the client read about a\n\nkilobyte past the end of the received message.\n\nThe option walk keeps a pointer and an offset in step, and the only bound check uses the offset:\n\n```c\n\n/* addons/dhcp/nxd_dhcp_client.c:7538, 7572 */\n\nwhile (i \u003c length - 1)\n\n{\n\n    ...\n    size = *(++data);      /* data moves 1: type -\u003e length byte */\n    data += size + 1;      /* data moves size + 1 more          */\n    i += size + 1;         /* i moves only size + 1             */\n\n}\n\n```\n\nA TLV option occupies size + 2 bytes. `data` is advanced by size + 2 in total, `i` by size + 1, so\n\nthe offset falls one byte behind the real read position for every option the walk skips. After\n\nenough skipped options the check `i \u003c length - 1` still holds while `data` is already past the end\n\nof the message, and the subsequent read of the type and length bytes comes from whatever follows.\n\nA single OFFER carrying a long run of skippable options is enough:\n\n```\n\nERROR: AddressSanitizer: heap-buffer-overflow\n\nREAD of size 1 at 0x61b000000794 thread T5\n\n    #0 _nx_dhcp_search_buffer     addons/dhcp/nxd_dhcp_client.c:7541\n    #1 _nx_dhcp_get_option_value  addons/dhcp/nxd_dhcp_client.c:7082\n\n0x61b000000794 is located 164 bytes to the right of 1648-byte region\n\n```\n\nA well formed OFFER through the same path is handled normally, the client records the offer and\n\nmoves to REQUESTING, so the difference is the option layout rather than the harness.\n\nThe read runs in the DHCP client thread while the client is still unconfigured, so it happens on\n\nevery boot in reach of a hostile DHCP responder. The values read are used to configure the\n\ninterface, which is how the disclosed bytes become observable.\n\nAdvance `i` by size + 2, or derive the bound from `data` rather than keeping a second counter.","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/netxduo","id":"CVE-2026-102720","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":"Memory corruption in NetX Duo","id":"CVE-2026-102721"},"packages":[],"prev":{"headline":"Weak cryptography in netxduo","id":"CVE-2026-102719"},"products":["eclipse-threadx/netxduo"],"published":"2026-09-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-29","vendors":["Eclipse Foundation"]},"summary":"A DHCP client flaw allows remote attackers to read memory past buffer boundaries via crafted DHCP offers, potentially disclosing sensitive data or causing crashes.","url":"https://insights.sbomify.com/CVE-2026-102720/"}