{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-102718 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-102718 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-102718 is a high-severity memory corruption vulnerability in Eclipse Foundation NetX Duo, published on 29 Sep 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-102718 and fix it if it is affected.\n\nWhat it is: CVE-2026-102718 is a high-severity memory corruption vulnerability in Eclipse Foundation NetX Duo, published on 29 Sep 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-102718 in the wild and no public exploit code.\n\nAffected product: Eclipse Foundation 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-102718/ (Markdown: https://insights.sbomify.com/CVE-2026-102718/index.md)","id":"CVE-2026-102718","markdown":"https://insights.sbomify.com/CVE-2026-102718/index.md","name":"CVE-2026-102718","record":{"aliases":["GHSA-7qmm-29vg-7hf8","GHSA-vhx3-6gpg-5fjw"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["denial_of_service","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"NetX Duo SNMP addon","requires_auth":"none","summary":"Remote attackers can cause denial of service or heap corruption in NetX Duo SNMP agents via crafted packets with invalid OID lengths.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"hey,\n\n`_nx_snmp_utility_object_id_get` in the NetX Duo SNMP addon does not validate the claimed OID data length against the actual buffer size when the OID uses BER multibyte length encoding, so a remote attacker can send a crafted SNMP packet with a multibyte OID length larger than the available buffer, causing the parser to read past the packet buffer boundary into adjacent heap memory. the OOB bytes are decoded as OID component values and written into the agents internal OID string buffer, corrupting agent state. on systems with memory protection the OOB read poses the risk of crashing the SNMP agent thread, causing denial of service. on bare metal embedded systems without memory protection the read silently succeeds and corrupts the agents internal state with heap data.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-10-13","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-10-13T15:16:04Z","kind":"github_poc","ref":"https://github.com/D7EAD/CVE-2026-102718","stars":1,"title":"Out-of-bounds read in the NetX Duo SNMP OID parser via a multi-byte BER length."}],"tier":"poc_unverified"},"has_fix":false,"headline":"Memory corruption in NetX Duo","id":"CVE-2026-102718","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":"Weak cryptography in netxduo","id":"CVE-2026-102719"},"packages":[],"prev":{"headline":"MQTT WebSocket setter ABI mismatch may disclose memory or cause a crash","id":"CVE-2026-102717"},"products":["NetX Duo"],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-29","vendors":["Eclipse Foundation"]},"summary":"Remote attackers can cause denial of service or heap corruption in NetX Duo SNMP agents via crafted packets with invalid OID lengths.","url":"https://insights.sbomify.com/CVE-2026-102718/"}