D3TN UD3TN up to 0.15.1 Administrative Record Parser heap-based overflow

Summaryinfo

A vulnerability was found in D3TN UD3TN up to 0.15.1. It has been rated as problematic. Affected is an unknown function of the component Administrative Record Parser. This manipulation causes heap-based overflow. This vulnerability is tracked as CVE-2026-121510. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in D3TN UD3TN up to 0.15.1. It has been declared as problematic. Affected by this vulnerability is an unknown function of the component Administrative Record Parser. The manipulation with an unknown input leads to a heap-based overflow vulnerability. The CWE definition for the vulnerability is CWE-122. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). As an impact it is known to affect availability. The summary by CVE is:

Remote Unauthenticated Heap Out-of-Bounds Write in µD3TN BPv6 Administrative Record Parser allows Unauthenticated Remote Attacker to Reliably Cause DoS

The advisory is shared at gitlab.com. This vulnerability is known as CVE-2026-121510 since 11/03/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.

Upgrading to version 0.15.2 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• D3TN

Name

• UD3TN

Version

• 0.15.0
• 0.15.1

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion