{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-25139 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-25139 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-25139 is a high-severity vulnerability in RIOT-OS RIOT, published on 4 Feb 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-25139 and fix it if it is affected.\n\nWhat it is: CVE-2026-25139 is a high-severity vulnerability in RIOT-OS RIOT, published on 4 Feb 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-25139 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-25139/ (Markdown: https://insights.sbomify.com/CVE-2026-25139/index.md)","id":"CVE-2026-25139","markdown":"https://insights.sbomify.com/CVE-2026-25139/index.md","name":"CVE-2026-25139","record":{"aliases":["GHSA-c8fh-23qr-97mc"],"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 IoT OS","requires_auth":"none","summary":"Unauthenticated attackers can read adjacent memory or crash devices via crafted 6LoWPAN fragments in RIOT OS.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"riot","vendor":"riot-os"}],"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":"RIOT is an open-source microcontroller operating system, designed to match the requirements of Internet of Things (IoT) devices and other embedded devices. In version 2025.10 and prior, multiple out-of-bounds read allow any unauthenticated user, with ability to send or manipulate input packets, to read adjacent memory locations, or crash a vulnerable device running the 6LoWPAN stack. The received packet is cast into a sixlowpan_sfr_rfrag_t struct and dereferenced without validating the packet is large enough to contain the struct object. At time of publication, no known patch exists.","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 Vulnerable to Multiple Out-of-Bounds Read When Processing Received 6LoWPAN SFR Fragments","id":"CVE-2026-25139","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"apko affected by potential unbounded resource consumption in expandapk.ExpandApk on attacker-controlled .apk streams","id":"CVE-2026-25140"},"packages":[],"prev":{"headline":"Rucio WebUI has Username Enumeration via Login Error Message","id":"CVE-2026-25138"},"products":["RIOT"],"published":"2026-02-04","related":[{"cvss_score":9.8,"headline":"Buffer overflows in RIOT","id":"CVE-2024-32017","kev_date_added":null,"published":"2024-05-01"},{"cvss_score":9.8,"headline":"RIOT-OS vulnerable to Out of Bounds Write in _rbuf_add","id":"CVE-2023-33975","kev_date_added":null,"published":"2023-05-30"},{"cvss_score":9.8,"headline":"RIOT-OS vulnerable to Buffer Overflow during IPHC receive","id":"CVE-2023-24819","kev_date_added":null,"published":"2023-04-24"},{"cvss_score":9.8,"headline":"RIOT-OS vulnerable to Packet Type Confusion during IPHC send","id":"CVE-2023-24823","kev_date_added":null,"published":"2023-04-24"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2021-27357","kev_date_added":null,"published":"2021-04-06"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2021-27697","kev_date_added":null,"published":"2021-04-06"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2021-27698","kev_date_added":null,"published":"2021-04-06"}],"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-02-04","vendors":["RIOT-OS"]},"summary":"Unauthenticated attackers can read adjacent memory or crash devices via crafted 6LoWPAN fragments in RIOT OS.","url":"https://insights.sbomify.com/CVE-2026-25139/"}