{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-107838 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-107838 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-107838 is a high-severity denial of service 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-107838 and fix it if it is affected.\n\nWhat it is: CVE-2026-107838 is a high-severity denial of service 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-107838 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-107838/ (Markdown: https://insights.sbomify.com/CVE-2026-107838/index.md)","id":"CVE-2026-107838","markdown":"https://insights.sbomify.com/CVE-2026-107838/index.md","name":"CVE-2026-107838","record":{"aliases":["GHSA-39j3-3v73-5mj2"],"analysis":{"component_type":"operating_system","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"RIOT OS","requires_auth":"none","summary":"Remote attackers can cause a denial of service in RIOT OS devices by triggering an assertion failure in the nanocoap fileserver when token extensions are enabled.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-617","name":"Reachable Assertion"},{"id":"CWE-252","name":"Unchecked Return Value"}],"description":"RIOT is an open-source microcontroller operating system designed for Internet of Things devices and other embedded systems. From version 2023.07 through version 2026.07, nanocoap_fileserver callers in sys/net/application_layer/nanocoap/fileserver.c ignore a failure returned by _resp_init() when coap_build_reply() cannot fit a response header into the response buffer. A remote client can send a CoAP request with a sufficiently large extended token when nanocoap_token_ext is enabled, causing response initialization to fail while _get_file() or _get_directory() continues with stale response state. The path then reaches _calc_szx2() and its pdu-\u003epayload_len \u003e reserve assertion, terminating the affected service or device task. No fixed 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: nanocoap_fileserver ignores response initialization failure, leading to reachable assertion","id":"CVE-2026-107838","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"ageLANServer: Unbounded JSON Array Allocation in AoE3 Cloud `getFileURL` Endpoint Leads to Remote Denial of Service","id":"CVE-2026-107839"},"packages":[],"prev":{"headline":"RIOT: Out-of-Bounds Read in RIOT OS 6LoWPAN SFF Fragment Handling","id":"CVE-2026-107837"},"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 cause a denial of service in RIOT OS devices by triggering an assertion failure in the nanocoap fileserver when token extensions are enabled.","url":"https://insights.sbomify.com/CVE-2026-107838/"}