D3TN Ud3tn up to 0.15.1 BPv6-BPv7 Fragmenter out-of-bounds
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.37+ |
Summary
A vulnerability identified as problematic has been detected in D3TN Ud3tn up to 0.15.1. Affected by this issue is some unknown functionality of the component BPv6-BPv7 Fragmenter. Performing a manipulation results in out-of-bounds. This vulnerability is cataloged as CVE-2026-121511. The attack must be initiated from a local position. There is no exploit available. You should upgrade the affected component.
Details
A vulnerability classified as problematic has been found in D3TN Ud3tn up to 0.15.1. This affects some unknown functionality of the component BPv6-BPv7 Fragmenter. The manipulation with an unknown input leads to a out-of-bounds vulnerability. CWE is classifying the issue as CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Heap Out-of-Bounds Read in µD3TN BPv6/BPv7 Fragmenter allows Local Attacker to Read Memory and Reliably Cause DoS
It is possible to read the advisory at gitlab.com. This vulnerability is uniquely identified as CVE-2026-121511 since 11/03/2026. The exploitability is told to be easy. Attacking locally is a requirement. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 0.15.2 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.2VulDB Meta Temp Score: 6.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.1
CNA Vector (GitLab): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Out-of-boundsCWE: CWE-125 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Ud3tn 0.15.2
Timeline
11/03/2026 Advisory disclosed11/03/2026 CVE reserved
11/03/2026 VulDB entry created
11/03/2026 VulDB entry last update
Sources
Advisory: gitlab.comStatus: Confirmed
CNA: GitLab
CVE: CVE-2026-121511 (🔒)
GCVE (CVE): GCVE-0-2026-121511
GCVE (VulDB): GCVE-100-430299
Entry
Created: 11/03/2026 15:42Changes: 11/03/2026 15:42 (63)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.