CVE-2026-49868

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

GHSA-p3fx-9qcg-jmcf ↗EUVD-2026-102947 ↗

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 <= 2026.04
fixed in fc1ff4ccd54fafa0045dfa11de5ecbacecb7a43a
CWE-125 Out-of-bounds Read
ETK-2026-1796Zero's internal tracking ID, independent of the CVE number., permanent identifier
4d 11h 45msince last run
25mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h11m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

RIOT versions before 2026.07 mishandle certain DHCPv6 reply option lengths in the DHCPv6 client. A malicious or compromised DHCPv6 server can cause affected devices to crash and may be able to expose or corrupt memory when IA_PD support is enabled.

mitigation

Upgrade RIOT to version 2026.07 or later. Where an immediate upgrade is not possible, disable the affected DHCPv6 IA_PD client functionality and restrict access to trusted DHCPv6 servers.

fixed in fc1ff4ccd54fafa0045dfa11de5ecbacecb7a43a

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.
contextual
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.37%29th percentile
agent run time
25m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-16 16:50Z
Δ 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

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-16 16:50Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1796",
  "cve_id": "CVE-2026-49868",
  "display_id": "CVE-2026-49868",
  "ghsa_id": "GHSA-p3fx-9qcg-jmcf",
  "euvd_id": "EUVD-2026-102947",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Out-of-bounds read in RIOT DHCPv6 client",
  "summary": "RIOT versions before 2026.07 mishandle certain DHCPv6 reply option lengths in the DHCPv6 client. A malicious or compromised DHCPv6 server can cause affected devices to crash and may be able to expose or corrupt memory when IA_PD support is enabled.",
  "mitigation": "Upgrade RIOT to version 2026.07 or later. Where an immediate upgrade is not possible, disable the affected DHCPv6 IA_PD client functionality and restrict access to trusted DHCPv6 servers.",
  "vendor": "RIOT-OS",
  "product": "RIOT",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 2026.04"
      ],
      "ecosystem": "riot",
      "fixed_versions": [
        "fc1ff4ccd54fafa0045dfa11de5ecbacecb7a43a"
      ],
      "package_name": "RIOT",
      "purl": null
    }
  ],
  "cwes": [
    125
  ],
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0037,
  "epss_percentile": 0.2962,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 24.98814691666667,
  "t0_at": "2026-10-16T16:50:58.750000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-16T16:50:58.750000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-16T16:50:58.750000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-49868"
    }
  }
}

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