Skip to content

Pion DTLS's usage of random nonce generation with AES GCM ciphers risks leaking the authentication key

Moderate severity GitHub Reviewed Published Feb 10, 2026 in pion/dtls • Updated Feb 13, 2026

Package

gomod github.com/pion/dtls (Go)

Affected versions

<= 1.5.4

Patched versions

None
gomod github.com/pion/dtls/v2 (Go)
<= 2.2.12
None
gomod github.com/pion/dtls/v3 (Go)
= 3.1.0
< 3.0.11
3.1.1
3.0.11

Description

Impact

Pion DTLS versions v1.0.0 through v3.0.10 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".

Patches

Upgrade to v3.1.1 or later. This version includes PR #796, which uses the 64-bit sequence number to populate the nonce_explicit part of the GCM nonce. This is according to best practice outlined in RFC 9325 section 7.2.1.

v3.0.11 is a backport patch supporting Go v1.21

Workarounds

There are no workarounds without upgrading to version v3.0.11, v3.1.1 or later.

References

Commit fixing the bug: pion/dtls@61762de
Commit fixing the bug (backport): 90e241c
Pull request: #796

References

@theodorsm theodorsm published to pion/dtls Feb 10, 2026
Published to the GitHub Advisory Database Feb 11, 2026
Reviewed Feb 11, 2026
Published by the National Vulnerability Database Feb 11, 2026
Last updated Feb 13, 2026

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(17th percentile)

Weaknesses

Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Learn more on MITRE.

CVE ID

CVE-2026-26014

GHSA ID

GHSA-9f3f-wv7r-qc8r

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.