Skip to main content

µD3TN EUVDEUVD-2026-115832

| CVE-2026-121512 HIGH
Memory Leak (CWE-401)
2026-11-03 GitLab GHSA-3c5c-mq57-gwpx
7.5
CVSS 3.1 · Vendor: GitLab
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach µD3TN node processing BPv6
  2. Delivery
    Send crafted bundles with EID references
  3. Exploit
    Trigger amplified per-request memory leak
  4. Execution
    Repeat to exhaust node memory
  5. Impact
    Denial of service to DTN traffic

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Resource cleanup, leak prevention
Exploitation Conditions

Exploitation requires that a µD3TN node be network-reachable and actively processing Bundle Protocol version 6 (BPv6) bundles, since the flaw is in BPv6 EID reference handling; a node restricted to BPv7 or not exposed to attacker-originated bundles would not be reachable through this path. No authentication or user interaction is needed (PR:N/UI:N). The amplification property means an attacker needs relatively little traffic to cause disproportionate memory consumption, but impact is limited to availability - no confidentiality or integrity effect (C:N/I:N). The precise malformed EID reference that triggers the leak is not described in the available sources, and no fixed version is listed in the provided data.

Impact

The signals point to a genuine but moderate-urgency availability issue rather than a top-tier emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5) describes a remotely reachable, low-complexity flaw needing no privileges or user interaction and affecting only availability - consistent with CWE-401 (missing release of memory) and the 'Memory Leak with Amplification' description, where small attacker inputs disproportionately consume server memory. The vuln.today decision label is 'this_week', not 'act_now' or 'emergency', so prioritize remediation within the week rather than treating it as drop-everything. No EPSS score, no CISA KEV entry, and no confirmed exploit code are present in the input, so there is no evidence of active or widespread exploitation; this is currently a severity-driven priority, not an exploitation-driven one. The main factor lowering real-world risk is deployment footprint: µD3TN is a niche Delay/Disruption-Tolerant Networking (Bundle Protocol) implementation, so exposure is limited to the relatively small population running it with BPv6 processing reachable. One data conflict to note: the input Tags include 'Information Disclosure', but the CVSS vector shows C:N/I:N/A:H and the description is a DoS - the confidentiality label is inconsistent with the vector and should be disregarded. EPSS and SSVC automatable/technical-impact fields were not supplied, so those dimensions could not be weighed.

Exploit ScenarioDerived

A remote, unauthenticated attacker who can reach a µD3TN node processing Bundle Protocol version 6 sends crafted bundles whose EID references trigger a memory leak that is amplified relative to the input size. By repeating these bundles, the attacker steadily exhausts the node's memory until it degrades or crashes, denying service to legitimate DTN traffic. No public exploit code is identified in the provided data; the referenced GitLab work item is the vendor issue tracker entry, not verified working exploit code.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Nov 03, 2026

Memory exhaustion through amplified BPv6 EID reference handling in µD3TN can let remote attackers degrade or crash a network-reachable node by sending crafted bundles, requiring no authentication or user interaction. The flaw is a CWE-401 memory leak affecting versions matched by the vendor CPE; the precise malformed EID reference is not described in the available sources, and no fixed version is listed. No public exploit identified at time of analysis and no CISA KEV entry is present, but the vendor work item and this_week priority warrant prompt triage for network-reachable BPv6 deployments.

RemediationAI

No vendor-released patch version is identified in the provided data; monitor https://gitlab.com/d3tn/ud3tn/-/work_items/292 for a fixed release and apply it when available. Until then, restrict network reachability to µD3TN BPv6 bundle-processing endpoints to trusted peers or networks via firewall ACLs, accepting that this does not remediate nodes that must accept bundles from untrusted sources. Where BPv6 interoperability is not required, use BPv7-only configurations, which the assessment says are not reachable through this path, at the cost of losing BPv6 compatibility. For exposed nodes that must remain on BPv6, add memory-usage monitoring and restart guardrails as containment; this does not fix the leak and can cause service interruption.

Affected VersionsENISA

µD3TN 0 <0.15.2

Affected Packages

euvd µd3tn fix: 0.15.2

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

µD3TN is a Delay-Tolerant Networking (DTN) implementation that processes Bundle Protocol bundles. In BPv6, endpoint identifiers (EIDs) are used to address bundle sources and destinations; handling references to those EIDs incorrectly can leave memory allocated after its effective lifetime, which is CWE-401. The assessed CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) describes a remotely reachable, low-complexity availability impact with no confidentiality or integrity effect. The amplification property means a relatively small amount of attacker traffic can produce disproportionate memory consumption, but the trigger is specifically BPv6 EID reference handling and the exact malformed reference is not described in available sources. Nodes restricted to BPv7 or not exposed to attacker-originated bundles are not reachable through this path per the assessment.

Know when D3Tn gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (GitLab) PRIMARY 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
vuln.today AI 7.5 HIGH

Remote unauthenticated attacker sends BPv6 bundles with no user interaction (AV:N/AC:L/PR:N/UI:N); impact is an amplified memory-exhaustion DoS, so A:H with C:N/I:N.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (GitLab).

CVSS VectorVendor: GitLab

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

2
Patch available
Nov 03, 2026 - 15:02 EUVD
CVE Published
Nov 03, 2026 - 14:18 cve.org
HIGH 7.5

DescriptionCVE.org

Memory Leak with Amplification in µD3TN BPv6 EID Reference Handling allows Unauthenticated Remote Attacker to Cause DoS

Executive ViewAI

Why It Matters

CVE-2026-121512 is a high-severity memory leak in µD3TN's BPv6 bundle processing that can allow remote, unauthenticated attackers to crash or degrade any network-reachable node. This directly threatens the availability of DTN-based communications, potentially disrupting mission-critical data relay and forcing costly incident response. Leadership should prioritize remediation because affected deployments may face service outages with no vendor patch currently available.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include: restricting network access to BPv6 interfaces to trusted peers only, implementing rate limiting or connection throttling for incoming bundles, enabling memory usage monitoring with automatic alerts, and preparing to restart or failover affected nodes if memory exhaustion is detected.

Threat Intelligence Overview

Prevalence
Low
niche DTN/Bundle Protocol implementation, limited research and aerospace deployment
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS N/A
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy