{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-102715 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-102715 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-102715 is a high-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-102715 and fix it if it is affected.\n\nWhat it is: CVE-2026-102715 is a high-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-102715 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-102715/ (Markdown: https://insights.sbomify.com/CVE-2026-102715/index.md)","id":"CVE-2026-102715","markdown":"https://insights.sbomify.com/CVE-2026-102715/index.md","name":"CVE-2026-102715","record":{"aliases":["GHSA-2gf7-5224-5vrj","GHSA-rp9p-ggxc-p9xm"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"ThreadX NetX Duo","requires_auth":"none","summary":"A heap buffer overflow in the mDNS responder allows remote attackers to corrupt memory or execute code via crafted network packets.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"Any host on the LAN can send two mDNS records and make the responder write past the end of its\n\ntransmit packet.\n\nThe string table stores each name in a slot rounded up to a multiple of four:\n\n```c\n\n/* addons/mdns/nxd_mdns.c:11436, 11443, 11447 */\n\nmemory_len = ((memory_len \u0026 0xFFFFFFFC) + 8) \u0026 0xFFFFFFFF;\n\n...\n\nlen = *((USHORT*)(p - 2));           /* slot size, not string length */\n\nif ((len == memory_len) \u0026\u0026 ... _nx_mdns_name_match(start, memory_ptr, memory_size) ...)\n\n```\n\nThe lookup that decides whether an incoming name is already stored compares the rounded slot size,\n\nso names of 12, 13, 14 and 15 characters share one bucket. A second name in the bucket is answered\n\nwith the pointer to the first, and the record then carries a string up to three bytes longer than\n\nthe length the caller accounted for. `_nx_mdns_packet_rr_add` (nxd_mdns.c:8911) sizes its only\n\nbound check from that stale length, and `_nx_mdns_name_string_encode` writes the real string.\n\nTwo PTR records are enough, both ordinary mDNS responses to a `_http._tcp` query, with owner names\n\nwhose lengths fall in the same bucket:\n\n```\n\n==87491==ERROR: AddressSanitizer: heap-buffer-overflow\n\nWRITE of size 1 at 0x611000000124 thread T5\n\n    #0 _nx_mdns_name_string_encode  addons/mdns/nxd_mdns.c:13096\n    #1 _nx_mdns_packet_rr_add       addons/mdns/nxd_mdns.c:8911\n\n0x611000000124 is 0 bytes to the right of 228-byte region\n\n```\n\nThe overflow is one to three bytes of attacker-influenced name data past `nx_packet_data_end`. In a\n\nnormal pool that lands in the next packet in the same pool rather than in a redzone, so the visible\n\neffect is a corrupted neighbouring packet or a corrupted pool free list rather than a clean crash.\n\nCompare the slot size against the stored string length before declaring a match, or keep the\n\nstring length in the slot header and return it to the caller so the encoder and the bound check\n\nagree.","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-102715","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":"Denial of service in eclipse-threadx/netxduo","id":"CVE-2026-102716"},"packages":[],"prev":{"headline":"Denial of service in NetX Duo","id":"CVE-2026-102714"},"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 heap buffer overflow in the mDNS responder allows remote attackers to corrupt memory or execute code via crafted network packets.","url":"https://insights.sbomify.com/CVE-2026-102715/"}