CVE-2026-124001

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

GHSA-rcqq-5qmv-7fxp ↗EUVD-2026-120227 ↗

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.
nasa-jpl ION-DTN 2.2.1b <= 4.2.0
fixed in 4.2.1-a.2
CWE-190 Integer Overflow or Wraparound
ETK-2026-3986Zero's internal tracking ID, independent of the CVE number., permanent identifier
1d 10h 42msince last run
52mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h18m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

ION-DTN versions 2.2.1b through 4.2.0 are affected in the Datagram Retransmission (DGR) convergence layer. An attacker able to supply crafted DGR traffic to the receive path may corrupt heap memory, causing a denial of service and potentially code execution. Exposure requires access through internal IPC or a configured custom transport that accepts the attacker’s traffic.

mitigation

Upgrade ION-DTN to 4.2.1-a.2 or later.

fixed in 4.2.1-a.2

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.
–
agent run time
52m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-09 18:45Z
Δ 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-11-09 18:45Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3986",
  "cve_id": "CVE-2026-124001",
  "display_id": "CVE-2026-124001",
  "ghsa_id": "GHSA-rcqq-5qmv-7fxp",
  "euvd_id": "EUVD-2026-120227",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Integer overflow in ION-DTN DGR datagram handling",
  "summary": "ION-DTN versions 2.2.1b through 4.2.0 are affected in the Datagram Retransmission (DGR) convergence layer. An attacker able to supply crafted DGR traffic to the receive path may corrupt heap memory, causing a denial of service and potentially code execution. Exposure requires access through internal IPC or a configured custom transport that accepts the attacker’s traffic.",
  "mitigation": "Upgrade ION-DTN to 4.2.1-a.2 or later.",
  "vendor": "nasa-jpl",
  "product": "ION-DTN",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "2.2.1b <= 4.2.0"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "4.2.1-a.2"
      ],
      "package_name": "ION-DTN",
      "purl": null
    }
  ],
  "cwes": [
    190
  ],
  "cvss_score": 9.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 51.82338248333333,
  "t0_at": "2026-11-09T18:45:25.184000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-09T18:45:25.184000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-09T18:45:25.184000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-124001"
    }
  }
}

published 2026-11-09 19:11Z
last change 2026-11-11 05:12Z

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.