Out-of-bounds Read in µD3TN
µD3TN versions before 0.15.2 running external dispatch without a dispatcher secret are exposed, and both BPv6 and BPv7 fragmenters carry the defect. Fixed in 0.15.2.
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
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Daemon runs with external dispatch enabled Affects both BPv6 and BPv7 fragmenters Daemon started without a dispatcher secret, so the AAP 2.0 control interface accepts unauthenticated connections
- Exploitation0/40No signal
- Exposure5/25Specific setups only
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
CVE-2026-121511 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (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? →
- 12/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? →
- Specific setups only
- 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: no
- Technical impact: partial
Summary
µD3TN, a delay-tolerant networking implementation that handles BPv6 and BPv7 bundle fragmentation, is affected by this flaw. A local attacker could read memory outside the intended heap buffer and reliably crash the software, causing a denial of service.
Read the original description
Heap Out-of-Bounds Read in µD3TN BPv6/BPv7 Fragmenter allows Local Attacker to Read Memory and Reliably Cause DoS
What to do
Check whether your setup matches what the bug needs.
Daemon runs with external dispatch enabled Affects both BPv6 and BPv7 fragmenters Daemon started without a dispatcher secret, so the AAP 2.0 control interface accepts unauthenticated connectionsUpgrade to a fixed version: 0.15.2.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · 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-121511
Is CVE-2026-121511 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 dispatcher can read µD3TN's heap memory beyond the bundle payload and have the contents forwarded to a next-hop node. An offset pointing before mapped memory terminates the process.Source: gitlab.com
Which versions are affected by CVE-2026-121511?
µD3TN: before 0.15.2.Source: cve.now feed data
Am I affected, and how do I check?
Versions before 0.15.2 are affected. The defect needs external dispatch enabled, and the AAP 2.0 control interface accepts unauthenticated connections when the daemon was started without a dispatcher secret. To check, confirm your version and whether external dispatch is enabled and a dispatcher secret was set at startup.Source: gitlab.com
How do I fix CVE-2026-121511?
Upgrade to µD3TN 0.15.2 or later, which contains the fix.Source: gitlab.com