# CVE-2026-84484: ION-DTN before 4.2.0 Out-of-Bounds Read via decodeSdnv

> Unauthenticated remote attackers can read memory via truncated SDNV values in ION-DTN, potentially exposing sensitive data.

- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-5vmj-4h65-2fh8, GHSA-85pw-28vw-2jf7

## What is CVE-2026-84484?

CVE-2026-84484 is a high-severity vulnerability in nasa-jpl ION-DTN, published on 2 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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. Attackers can send a UDP datagram to the LTP link service input port with a truncated SDNV to trigger reads up to nine bytes past buffer boundaries and underflow byte counters.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-84484?


## How do I fix CVE-2026-84484?

No fix has been published for CVE-2026-84484 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-84484 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-84484 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-84484 and fix it if it is affected.

What it is: CVE-2026-84484 is a high-severity vulnerability in nasa-jpl ION-DTN, published on 2 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-84484 exists.

Affected product: nasa-jpl ION-DTN. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-84484/ (Markdown: https://insights.sbomify.com/CVE-2026-84484/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-84484
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-84484
- OSV: https://osv.dev/vulnerability/CVE-2026-84484

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-84484/
Summaries are generated and may contain mistakes; the official description above is the record.