Out-of-bounds Write in µD3TN
µD3TN versions before 0.15.2 with the tcpspp convergence layer enabled are exposed. The fix is in 0.15.2. No vendor severity rating is given.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.15.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.15.2.
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Data gap: Advisories don't say whether default setups are affected
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
- Would score about 33 if advisories confirm default setups are exposed
CVE-2026-121513 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.5 (high) and affects µD3TN; fixed in 0.15.2.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 28/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 0.15.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
µD3TN, a delay-tolerant networking software, is affected by a memory flaw in its SPP (Space Packet Protocol) parser. An unauthenticated remote attacker can trigger a heap overflow to reliably crash the software, causing a denial of service.
Read the original description
Off-by-one Heap Overflow in µD3TN v0.15.1 SPP Parser allows Unauthenticated Remote Attacker to Reliably Cause DoS
What to do
Upgrade to a fixed version: 0.15.2.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- D3TN GmbH µD3TN
fixed in 0.15.2
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121513
Is CVE-2026-121513 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A crafted SPP frame with a secondary header sent over the tcpspp convergence layer causes an off-by-one heap overflow. This corrupts the daemon heap and reliably crashes the daemon, stopping service to all connected applications and peers.Source: gitlab.com
Which versions are affected by CVE-2026-121513?
µD3TN: before 0.15.2.Source: cve.now feed data
Am I affected, and how do I check?
Versions from 0 up to but not including 0.15.2 are listed as affected, along with upstream master at commit ea56c6fb695044b1d05b965b545760ad36da25a1. The setup must have the tcpspp convergence layer enabled, so check the build version and whether tcpspp is enabled in the configuration.Source: gitlab.com
How do I fix CVE-2026-121513?
Upgrade to µD3TN 0.15.2 or later. Builds made from the affected upstream master commit should be updated to a release that includes the fix.Source: gitlab.com