PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-75584 nasa-jpl CVE debrief

A denial of service vulnerability exists in ION-DTN before 4.2.1-a.1. Unauthenticated remote attackers can crash the ION process by sending a BPv7 bundle with a zero-length payload. The issue arises from the canonicalizePayloadBlock() function in bpsec_util.c, which passes bundle->payload.length to zco_clone() without validating it against zero. This causes a failed CHKZERO assertion that triggers sm_Abort() and terminates the process with SIGABRT before any HMAC verification occurs.

Vendor
nasa-jpl
Product
ION-DTN
CVSS
HIGH 8.7
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-10
Original CVE updated
2026-09-18
Advisory published
2026-09-10
Advisory updated
2026-09-18

Who should care

Defenders and administrators responsible for ION-DTN installations should assess exposure and prioritize patching to prevent potential denial of service attacks. ION-DTN operators, platform administrators, and security teams need to verify the ION-DTN version and apply patches. Vulnerability management and security teams should review configurations and monitor for potential denial of service attacks.

Why it matters

Defenders should prioritize verifying the ION-DTN version and applying patches to prevent potential denial of service attacks. The vulnerability allows unauthenticated remote attackers to crash the ION process, and its impact on mission-critical systems and services requires verification and mitigation.

  • Potential denial of service attacks against ION-DTN installations
  • Verification of ION-DTN version and patch level is required
  • Potential impact on mission-critical systems and services

Technical summary

The canonicalizePayloadBlock() function in bpsec_util.c passes bundle->payload.length to zco_clone() without validating it against zero, causing a failed CHKZERO assertion that triggers sm_Abort() and terminates the process with SIGABRT before any HMAC verification occurs. This issue affects ION-DTN before 4.2.1-a.1, allowing unauthenticated remote attackers to crash the ION process by sending a BPv7 bundle with a zero-length payload. The vulnerability requires no valid key or credential to exploit and impacts mission-critical systems and services.

Defensive priority

Defenders should prioritize verifying the ION-DTN version and applying patches to prevent potential denial of service attacks.

Recommended defensive actions

  • Verify ION-DTN version and apply patches
  • Review and update configurations to prevent exploitation
  • Monitor for potential denial of service attacks
  • Perform vulnerability assessment and prioritize patching
  • Review compensating controls for exposed systems
  • Check relevant monitoring, detection, and logs for exposed assets
  • Track exceptions and retest remediated assets

Evidence notes

The CVE record and NVD entry provide details about the vulnerability. Further verification is needed to determine the exact scope of affected versions and potential impact. Defenders should verify ION-DTN version and patch level, review configurations, and monitor for potential denial of service attacks. Evidence from the CVE Program and NVD detail page supports this assessment, but additional source references may be necessary to fully understand the vulnerability.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-75584 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-75584

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-75584 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-75584

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.