Skip to content
Networks

CVE-2026-84484

8.7
High
EPSS 0.48%Patch availableSep 2, 2026

Out-of-bounds read in ION-DTN decodeSdnv allows remote memory disclosure via truncated SDNVs.

common questions

Is CVE-2026-84484 being exploited?

Not confirmed. CVE-2026-84484 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.48% probability of exploitation in the next 30 days.

How severe is CVE-2026-84484?

CVE-2026-84484 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-84484?

Yes. A fix has been recorded for CVE-2026-84484. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-84484 affect?

CVE-2026-84484 affects NASA JPL ION-DTN (< 4.2.0), Systems using ION-DTN LTP link service, DTN/Delay-Tolerant Networking deployments. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-84484?

Upgrade to ION-DTN 4.2.0; block or filter LTP UDP input until patched.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
NASA JPL ION-DTN (< 4.2.0)Systems using ION-DTN LTP link serviceDTN/Delay-Tolerant Networking deployments
impact

Unauthenticated remote OOB read via truncated SDNV over UDP (LTP port); can leak up to 9 bytes, underflow counters, or crash service (DoS).

action required

Patch when possible

affected versions
nasa-jpl ION-DTN
  • affected< 4.2.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free