# CVE-2026-59692: Gstreamer1-plugins-bad-free: gstreamer: dtls certificate subject dn stack buffer overflow in openssl_verify_callback

> A remote attacker can cause a denial of service by sending a certificate with an oversized Subject DN, triggering a stack buffer overflow in the GStreamer DTLS plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Jul 2026
- **Updated:** 10 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-59692, ECHO-215d-21ac-ab46, GHSA-f48p-mg4r-fhww, UBUNTU-CVE-2026-59692

## What is CVE-2026-59692?

CVE-2026-59692 is a high-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A stack buffer overflow vulnerability was found in GStreamer's 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: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2026-59692?


## How do I fix CVE-2026-59692?

Apply the vendor's patch.

## Is CVE-2026-59692 being exploited?

There is no known exploitation of CVE-2026-59692 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-59692 and fix it if it is affected.

What it is: CVE-2026-59692 is a high-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-59692 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-59692/ (Markdown: https://insights.sbomify.com/CVE-2026-59692/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-59692
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-59692
- OSV: https://osv.dev/vulnerability/CVE-2026-59692

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-59692/
Summaries are generated and may contain mistakes; the official description above is the record.