CVE-2026-107837

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

GHSA-m8mc-q4p7-p8j3 ↗EUVD-2026-95932 ↗

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 master (tested on current master branch)
CWE-125 Out-of-bounds Read
ETK-2026-1091Zero's internal tracking ID, independent of the CVE number., permanent identifier
11d 09h 34msince last run
16mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h23m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

RIOT versions 2026.07 and earlier can read past a packet buffer while handling certain 6LoWPAN fragments. An attacker able to send malformed 6LoWPAN traffic may expose memory contents or cause the network stack to crash.

mitigation

Restrict 6LoWPAN traffic to trusted peers and networks, or disable the affected 6LoWPAN functionality where it is not needed. Monitor RIOT upstream for a corrected release; no fixed version is 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.38%30th percentile
agent run time
16m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-09 17:53Z
Δ 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:53Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1091",
  "cve_id": "CVE-2026-107837",
  "display_id": "CVE-2026-107837",
  "ghsa_id": "GHSA-m8mc-q4p7-p8j3",
  "euvd_id": "EUVD-2026-95932",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Out-of-bounds read in RIOT 6LoWPAN fragment processing",
  "summary": "RIOT versions 2026.07 and earlier can read past a packet buffer while handling certain 6LoWPAN fragments. An attacker able to send malformed 6LoWPAN traffic may expose memory contents or cause the network stack to crash.",
  "mitigation": "Restrict 6LoWPAN traffic to trusted peers and networks, or disable the affected 6LoWPAN functionality where it is not needed. Monitor RIOT upstream for a corrected release; no fixed version is recorded.",
  "vendor": "RIOT-OS",
  "product": "RIOT",
  "affected": [
    {
      "affected_notes": [
        "master (tested on current master branch)"
      ],
      "affected_ranges": [],
      "ecosystem": "riot-os/riot",
      "fixed_versions": [],
      "package_name": "RIOT OS",
      "purl": null
    }
  ],
  "cwes": [
    125
  ],
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H",
  "epss_score": 0.0038,
  "epss_percentile": 0.303,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 15.579028983333334,
  "t0_at": "2026-10-09T17:53:47.707000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-09T17:53:47.707000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-09T17:53:47.707000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-107837"
    }
  }
}

published 2026-10-09 19:00Z
last change 2026-10-21 04:45Z

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.