CVE-2026-107838

waiting for further signalsZero needs more public information before it can validate it.

GHSA-39j3-3v73-5mj2 ↗EUVD-2026-95933 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
RIOT-OS RIOT Since 2023.07
CWE-252 Unchecked Return Value
ETK-2026-1106Zero's internal tracking ID, independent of the CVE number., permanent identifier
11d 06h 47msince last run
45mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+5h05m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

RIOT versions 2023.07 through 2026.07 can terminate a nanocoap_fileserver service or device task after processing a malformed CoAP request. Exposure requires nanocoap_token_ext to be enabled and an attacker able to reach the affected CoAP service.

mitigation

Disable nanocoap_token_ext where it is not required, and restrict access to CoAP services to trusted networks or clients. Monitor RIOT for an updated release, as no fixed version is currently recorded.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.34%25th percentile
agent run time
45m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-09 17:55Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-09 17:55Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-107838

{
  "etk_id": "ETK-2026-1106",
  "cve_id": "CVE-2026-107838",
  "display_id": "CVE-2026-107838",
  "ghsa_id": "GHSA-39j3-3v73-5mj2",
  "euvd_id": "EUVD-2026-95933",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Remote denial of service in RIOT nanocoap_fileserver",
  "summary": "RIOT versions 2023.07 through 2026.07 can terminate a nanocoap_fileserver service or device task after processing a malformed CoAP request. Exposure requires nanocoap_token_ext to be enabled and an attacker able to reach the affected CoAP service.",
  "mitigation": "Disable nanocoap_token_ext where it is not required, and restrict access to CoAP services to trusted networks or clients. Monitor RIOT for an updated release, as no fixed version is currently recorded.",
  "vendor": "RIOT-OS",
  "product": "RIOT",
  "affected": [
    {
      "affected_notes": [
        "Since 2023.07"
      ],
      "affected_ranges": [],
      "ecosystem": "riot os",
      "fixed_versions": [],
      "package_name": null,
      "purl": null
    }
  ],
  "cwes": [
    252
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": 0.0034,
  "epss_percentile": 0.2588,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 44.57565843333333,
  "t0_at": "2026-10-09T17:55:34.670000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-09T17:55:34.670000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-09T17:55:34.670000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-107838"
    }
  }
}

published 2026-10-09 22:16Z
last change 2026-10-21 05:31Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.