CVE-2026-26014 Details
Description
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.
A vulnerability exists in Pion DTLS, a Go implementation of Datagram Transport Layer Security, in versions 1.0.0 prior to 3.1.0. The issue arises from the use of random nonce generation with AES GCM ciphers, which can lead to the leakage of the authentication key. Remote attackers could exploit this vulnerability to spoof data by taking advantage of nonce reuse within a session, executing what is known as a 'forbidden attack'.
Users are advised to upgrade to Pion DTLS version 3.1.0 or later, which addresses the vulnerability by implementing proper nonce generation practices for GCM ciphers. Instructions for upgrading can be found in the Pion DTLS repository on GitHub.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Feb 12, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
| CWE-200 | Exposure of Sensitive Information to an Unauthorized Actor | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| pion dtls | < 3.1.0 |
CPE
Remediation
| |
Change History
6 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Feb 25, 2026 | Reanalysis | [email protected] |
| Feb 13, 2026 | Initial Analysis | [email protected] |
| Feb 13, 2026 | CVE Modified | [email protected] |
| Feb 11, 2026 | New CVE Received | [email protected] |