CVE-2026-102692

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

GHSA-8365-gj33-rgpf ↗EUVD-2026-102945 ↗

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 (commit aeeae69e)
CWE-190 Integer Overflow or Wraparound
ETK-2026-1797Zero's internal tracking ID, independent of the CVE number., permanent identifier
4d 22h 07msince last run
1h 12mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h11m
0
+4h
+6h
+8h
+10h
+12h

description

RIOT releases before 2026.07 are affected by an integer overflow in nanocoap processing of CoAP Block2 option values on 32-bit targets. A remote unauthenticated CoAP client may cause out-of-bounds memory access, denial of service, or memory corruption by sending an oversized Block2 value.

mitigation

Upgrade RIOT to version 2026.07 or later. Until upgrades are complete, restrict CoAP access to trusted clients and networks.

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.35%27th percentile
agent run time
1h 12m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-16 16:48Z
Δ 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-16 16:48Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1797",
  "cve_id": "CVE-2026-102692",
  "display_id": "CVE-2026-102692",
  "ghsa_id": "GHSA-8365-gj33-rgpf",
  "euvd_id": "EUVD-2026-102945",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Integer overflow in RIOT nanocoap Block2 handling",
  "summary": "RIOT releases before 2026.07 are affected by an integer overflow in nanocoap processing of CoAP Block2 option values on 32-bit targets. A remote unauthenticated CoAP client may cause out-of-bounds memory access, denial of service, or memory corruption by sending an oversized Block2 value.",
  "mitigation": "Upgrade RIOT to version 2026.07 or later. Until upgrades are complete, restrict CoAP access to trusted clients and networks.",
  "vendor": "RIOT-OS",
  "product": "RIOT",
  "affected": [
    {
      "affected_notes": [
        "<= master (commit aeeae69e)"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "RIOT",
      "purl": null
    }
  ],
  "cwes": [
    190
  ],
  "cvss_score": 9.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H",
  "epss_score": 0.0035,
  "epss_percentile": 0.2724,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 71.83979121666667,
  "t0_at": "2026-10-16T16:48:35.776000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-16T16:48:35.776000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-16T16:48:35.776000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-102692"
    }
  }
}

published 2026-10-16 17:47Z
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.