µD3TN EUVD-2026-115830

The target must be a µD3TN node that receives and parses Bundle Protocol version 6 (BPv6) administrative records and is reachable by the attacker over the network; the flaw is in that specific BPv6 administrative-record parsing path. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N) no authentication or user interaction is required against such a node. Limiting factors: exploitation is constrained to deployments that actually process BPv6 (as opposed to BPv7-only configurations) and to attackers positioned to send bundles to the node; impact is limited to denial of service (A:H; C:N/I:N) with no evidence of code execution. The exact malformed-record condition that triggers the out-of-bounds write is not described in the available sources.

Signals point to a moderate-priority availability issue rather than a top-tier emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, A:H only) describes a remotely reachable, low-complexity, unauthenticated flaw with impact confined to availability - no confidentiality or integrity loss - consistent with the stated DoS outcome and CWE-787 (out-of-bounds write) that the vendor says reliably crashes the service rather than achieving code execution. The vuln.today decision label is 'this_week' (not act_now/emergency). There is no CISA KEV listing and no EPSS score supplied, so there is no evidence of active or probable widespread exploitation; absence of these is not proof of safety but means no exploitation pressure is confirmed. No POC or exploit reference is marked in the input (the sole reference is the GitLab work item tracking the issue, i.e. the advisory itself, not working exploit code). The dominant mitigating factor is real-world footprint: µD3TN is a niche Delay-Tolerant Networking Bundle Protocol implementation, so a network-vector unauthenticated DoS is serious for the small population that runs it but is not a broad internet-scale threat. Net: a genuine, promptly-patchable availability bug for operators of µD3TN handling BPv6 traffic, not a high-CVSS-but-irrelevant finding, yet also not an emergency for the general fleet.

An attacker who can send Bundle Protocol v6 traffic to a reachable µD3TN node transmits a crafted BPv6 administrative record whose parsing triggers a heap out-of-bounds write, reliably crashing the daemon and denying the DTN service. No authentication or user interaction is required (PR:N/UI:N), and the low attack complexity (AC:L) makes the crash repeatable. No public exploit code is identified in the provided data; the trigger beyond 'administrative record parsing' is not detailed in the available sources.