Authentication-key disclosure via random GCM nonces
Published Feb 11, 2026 · Updated Feb 11, 2026
Information disclosure in Pion DTLS 1.0.0 through 3.0.10 and 3.1.0 allows remote attackers to recover an AES-GCM authentication key. The aead.encrypt path in pkg/crypto/ciphersuite/ciphersuite.go filled the eight-byte explicit GCM nonce with random bytes instead of the record epoch and sequence number, permitting nonce reuse under one key. The attack requires a nonce collision within one session and enough ciphertext for a forbidden attack; the published impact is limited to key disclosure.
Summary
What happened
Information disclosure in Pion DTLS 1.0.0 through 3.0.10 and 3.1.0 allows remote attackers to recover an AES-GCM authentication key. The aead.encrypt path in pkg/crypto/ciphersuite/ciphersuite.go filled the eight-byte explicit GCM nonce with random bytes instead of the record epoch and sequence number, permitting nonce reuse under one key. The attack requires a nonce collision within one session and enough ciphertext for a forbidden attack; the published impact is limited to key disclosure.
The record
- CVE
- CVE-2026-26014
- Published
- Feb 11, 2026
- Updated
- Feb 11, 2026
- Vendor
- Pion
- Product
- Pion DTLS
- Classifications
- CWE-200, T1040
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 11, 2026CVE publishedPublication date reported by the CVE source.
- Feb 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo