{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-107837 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-107837 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-107837 is a high-severity vulnerability in RIOT-OS RIOT, published on 9 Oct 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-107837 and fix it if it is affected.\n\nWhat it is: CVE-2026-107837 is a high-severity vulnerability in RIOT-OS RIOT, published on 9 Oct 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-107837 in the wild and no public exploit code.\n\nAffected product: RIOT-OS RIOT. 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-107837/ (Markdown: https://insights.sbomify.com/CVE-2026-107837/index.md)","id":"CVE-2026-107837","markdown":"https://insights.sbomify.com/CVE-2026-107837/index.md","name":"CVE-2026-107837","record":{"aliases":["GHSA-m8mc-q4p7-p8j3"],"analysis":{"component_type":"operating_system","fix_type":"no_fix_stated","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"RIOT OS","requires_auth":"none","summary":"Remote attackers can trigger out-of-bounds reads in RIOT OS 6LoWPAN handling, leading to memory disclosure and network stack crashes.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"RIOT is an open-source microcontroller operating system designed for Internet of Things devices and other embedded systems. In 2026.07 and earlier, _receive() in sys/net/gnrc/network_layer/sixlowpan/gnrc_sixlowpan.c can route an undersized packet into SFF fragment handling after only a minimal payload check. The code then interprets the packet as a sixlowpan_frag_t or larger fragment header without verifying that the packet snip contains the required bytes. A remote attacker can send a malformed 6LoWPAN fragment that causes gnrc_sixlowpan_frag_recv() to read beyond the packet buffer, potentially disclosing memory and crashing the network stack. No fixed repository release is available as of this review.","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":"RIOT: Out-of-Bounds Read in RIOT OS 6LoWPAN SFF Fragment Handling","id":"CVE-2026-107837","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"RIOT: nanocoap_fileserver ignores response initialization failure, leading to reachable assertion","id":"CVE-2026-107838"},"packages":[],"prev":{"headline":"RIOT: nanoCoAP Block2 client slice handling underflows on inconsistent server-controlled block size","id":"CVE-2026-107836"},"products":["RIOT"],"published":"2026-10-09","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-13","vendors":["RIOT-OS"]},"summary":"Remote attackers can trigger out-of-bounds reads in RIOT OS 6LoWPAN handling, leading to memory disclosure and network stack crashes.","url":"https://insights.sbomify.com/CVE-2026-107837/"}