CVE-2026-114408

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

GHSA-xjgr-2wmf-f78j ↗EUVD-2026-115231 ↗

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.
Eclipse Foundation Eclipse ThreadX >= 6.4.5.202504, <= 6.5.2.202603a
fixed in 6.5.2.202603b
CWE-252 Unchecked Return Value
ETK-2026-3296Zero's internal tracking ID, independent of the CVE number., permanent identifier
4h 27msince 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+1h59m
0
+4h
+6h
+8h
+10h
+12h

description

Eclipse ThreadX NetX Duo 6.4.5.202504 through 6.5.2.202603a is affected when built with IPv6 path MTU discovery enabled. A network-based attacker may halt network processing by exhausting destination-table capacity, provided the target faults on null-address access.

mitigation

Upgrade NetX Duo to 6.5.2.202603b or later.

fixed in 6.5.2.202603b

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.
–
agent run time
45m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-02 15:04Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-02 15:04Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3296",
  "cve_id": "CVE-2026-114408",
  "display_id": "CVE-2026-114408",
  "ghsa_id": "GHSA-xjgr-2wmf-f78j",
  "euvd_id": "EUVD-2026-115231",
  "status": "published",
  "anchor_state": "anchored",
  "title": "NULL pointer dereference in Eclipse ThreadX NetX Duo ICMPv6 handling",
  "summary": "Eclipse ThreadX NetX Duo 6.4.5.202504 through 6.5.2.202603a is affected when built with IPv6 path MTU discovery enabled. A network-based attacker may halt network processing by exhausting destination-table capacity, provided the target faults on null-address access.",
  "mitigation": "Upgrade NetX Duo to 6.5.2.202603b or later.",
  "vendor": "Eclipse Foundation",
  "product": "Eclipse ThreadX",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 6.4.5.202504, <= 6.5.2.202603a"
      ],
      "ecosystem": "eclipse threadx",
      "fixed_versions": [
        "6.5.2.202603b"
      ],
      "package_name": "NetX Duo",
      "purl": null
    }
  ],
  "cwes": [
    252
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 44.839974,
  "t0_at": "2026-11-02T15:04:39.505000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-02T15:04:39.505000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-02T15:04:39.505000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-114408"
    }
  }
}

published 2026-11-02 16:18Z
last change 2026-11-02 19:27Z

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.