CVE-2026-59692

A stack buffer overflow vulnerability was found in GStreamers DTLS plugin. During a DTLS handshake, the peer certificate Subject Distinguished Name is printed into a fixed-size 2048-byte stack buffer without bounds checking. A remote unauthenticated attacker can send a certificate with an oversized Subject DN that exceeds the buffer, causing a stack buffer overflow and process crash, resulting in denial of service.

Weakness

A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).

Affected Software

Name	Vendor	Start Version	End Version
Red Hat Enterprise Linux 10	RedHat	gstreamer1-plugins-bad-free-0:1.26.7-2.el10_2.6	*
Red Hat Enterprise Linux 10.0 Extended Update Support	RedHat	gstreamer1-plugins-bad-free-0:1.24.11-3.el10_0.6	*
Red Hat Enterprise Linux 7 Extended Lifecycle Support	RedHat	gstreamer1-plugins-bad-free-0:1.10.4-7.el7_9	*
Red Hat Enterprise Linux 8	RedHat	gstreamer1-plugins-bad-free-0:1.16.1-9.el8_10.1	*
Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support	RedHat	gstreamer1-plugins-bad-free-0:1.16.1-4.el8_6.4	*
Red Hat Enterprise Linux 8.6 Extended Update Support Long-Life Add-On	RedHat	gstreamer1-plugins-bad-free-0:1.16.1-4.el8_6.4	*
Red Hat Enterprise Linux 8.8 Telecommunications Update Service	RedHat	gstreamer1-plugins-bad-free-0:1.16.1-4.el8_8.4	*
Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions	RedHat	gstreamer1-plugins-bad-free-0:1.16.1-4.el8_8.4	*
Red Hat Enterprise Linux 9	RedHat	gstreamer1-plugins-bad-free-0:1.22.12-7.el9_8.3	*
Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions	RedHat	gstreamer1-plugins-bad-free-0:1.22.1-6.el9_4.6	*
Red Hat Enterprise Linux 9.6 Extended Update Support	RedHat	gstreamer1-plugins-bad-free-0:1.22.12-5.el9_6.6	*
Gst-plugins-bad1.0	Ubuntu	questing	*

Potential Mitigations

Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking.
D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
Run or compile the software using features or extensions that randomly arrange the positions of a program’s executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code.
Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as “rebasing” (for Windows) and “prelinking” (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking.
For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335].

NVD	https://nvd.nist.gov/vuln/detail/CVE-2026-59692
CWE	https://cwe.mitre.org/data/definitions/121.html

Stack-based Buffer Overflow

Weakness

Affected Software

Potential Mitigations

References