PatchSiren cyber security CVE debrief
CVE-2026-84484 nasa-jpl CVE debrief
ION-DTN versions before 4.2.0 contain an out-of-bounds read vulnerability in the decodeSdnv function that allows unauthenticated remote attackers to read memory by sending truncated SDNV values. This vulnerability can be triggered by sending a UDP datagram to the LTP link service input port with a truncated SDNV, potentially reading up to nine bytes past buffer boundaries and underflowing byte counters. The affected product is ION-DTN, and the vulnerability has a high CVSS score of 8.7.
- Vendor
- nasa-jpl
- Product
- ION-DTN
- CVSS
- HIGH 8.7
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-02
- Original CVE updated
- 2026-09-04
- Advisory published
- 2026-09-02
- Advisory updated
- 2026-09-04
Who should care
ION-DTN users and administrators, network security teams, and vulnerability management teams should be aware of this high-severity vulnerability and take immediate action to assess and mitigate potential risks. Affected organizations should prioritize patching or updating ION-DTN to version 4.2.0 or later to prevent exploitation. Additionally, monitoring network traffic for suspicious UDP datagram activity and implementing compensating controls can help limit exposure to potential attacks. Security teams should review the official advisory and CVE record to validate affected scope, severity, and vendor guidance. They should also track exceptions, retest remediated assets, and close the item only after evidence is documented. Vulnerability management teams should inventory and assess ION-DTN installations for version 4.2.0 or later and apply patches or updates to address the vulnerability. Network security teams should review compensating controls for exposed systems while remediation is scheduled and verified. Asset owners should confirm whether affected product deployments exist in managed environments and assign an owner for follow-up. They should also plan vendor-supported updates or mitigations through normal change control where exposure is confirmed. Security teams should check relevant monitoring, detection, and logs for exposed assets that need extra review. They should also review the official advisory or CVE record to validate affected scope, severity, and vendor guidance. This vulnerability affects ION-DTN versions before 4.2.0 and has a high CVSS score of 8.7, indicating a high severity vulnerability that requires immediate attention. The vulnerability allows unauthenticated remote attackers to read memory by sending truncated SDNV values, potentially reading up to nine bytes past buffer boundaries and underflowing byte counters. The affected product is ION-DTN, and the vulnerability can be triggered by sending a UDP datagram to the LTP link service input port with a truncated SDNV. The vulnerability exists due to improper handling of SDNV values, allowing attackers to access memory beyond the buffer boundaries. The CVSS score of 8.7 indicates a high
Technical summary
The decodeSdnv function in ION-DTN versions before 4.2.0 contains an out-of-bounds read vulnerability. Unaffected remote attackers can exploit this by sending truncated SDNV values via UDP datagrams to the LTP link service input port, potentially reading up to nine bytes past buffer boundaries and underflowing byte counters. The vulnerability exists due to improper handling of SDNV values, allowing attackers to access memory beyond the buffer boundaries.
Defensive priority
High priority due to high CVSS score of 8.7 and potential for unauthenticated remote attacks.
Recommended defensive actions
- Inventory and assess ION-DTN installations for version 4.2.0 or later
- Apply patches or updates to ION-DTN to address the vulnerability
- Monitor network traffic for suspicious UDP datagram activity
- Implement compensating controls to limit exposure to potential attacks
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
Evidence notes
The vulnerability exists in ION-DTN versions before 4.2.0 in the decodeSdnv function, allowing unauthenticated remote attackers to read memory. Limited information is available on the exact scope of affected systems and potential attack vectors.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-84484 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-84484
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-84484 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-84484
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/nasa-jpl/ION-DTN
-
Source reference
Unverified legacy reference
URL: https://github.com/nasa-jpl/ION-DTN/blob/ion-open-source-4.1.4/ici/library/ion.c
-
Source reference
Unverified legacy reference
URL: https://github.com/nasa-jpl/ION-DTN/blob/ion-open-source-4.1.4/ici/library/platform.c
-
Source reference
Unverified legacy reference
URL: https://github.com/nasa-jpl/ION-DTN/commit/d52d22bdd383798712357f86a2778757f740e812
-
Source reference
Unverified legacy reference
URL: https://github.com/nasa-jpl/ION-DTN/releases/tag/ion-open-source-4.2.0
-
Source reference
Unverified legacy reference
URL: https://github.com/nasa-jpl/ION-DTN/security/advisories/GHSA-85pw-28vw-2jf7
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/ion-dtn-before-4.2.0-out-of-bounds-read-via-decodesdnv
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.