CVE-2026-26014GO-2026-4479GHSA-9F3F-WV7R-QC8R
Pion DTLS uses random nonce generation with AES GCM ciphers risks leaking the authentication key
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.0.11, 3.1.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Pion DTLS is a Go implementation of Datagram Transport Layer Security. Pion DTLS versions v1.0.0 through v3.0.10 and 3.1.0 use random nonce generation with AES GCM ciphers, which makes it easier for remote attackers to obtain the authentication key and spoof data by leveraging the reuse of a nonce in a session and a "forbidden attack". Upgrade to v3.0.11, v3.1.1, or later.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- pion dtls
fixed in 3.0.11
- github.com/pion/dtlsGo
All versions
- github.com/pion/dtls/v2Go
All versions
- github.com/pion/dtls/v3Go
From 3.0.10 · fixed in 3.0.11; From 3.1.0 · fixed in 3.1.1
- github.com/pion/dtls/v3Go
From 3.1.0 · fixed in 3.1.1
- github.com/pion/dtls/v2Go
through 2.2.12
- github.com/pion/dtlsGo
through 1.5.4
- github.com/pion/dtls/v3Go
fixed in 3.0.11