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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.9 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2026-26014: 0.70% estimated exploitation activity in the next 30 days; percentile 53.11 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 nonceexplicit 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: https://github.com/pion/dtls/commit/61762dee8217991882c5eb79856b9e7a73ee349f Commit fixing the bug (backport): 90e241c Pull request: #796

Published by the source

11 Feb 2026, 15:13 UTC

Last modified by the source

13 Feb 2026, 14:18 UTC

Source last checked

26 Oct 2026, 15:14 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-9f3f-wv7r-qc8r

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-26014

Advisory: Pion DTLS's usage of random nonce generation with AES GCM ciphers risks leaking the authentication key
IDs: CVE-2026-26014, GHSA-9f3f-wv7r-qc8r
Record: https://patchnext.com/advisories/cve-2026-26014 (revision 1, source checked 26 Oct 2026, 15:14 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/pion/dtls/v3 3.1.1, 3.0.11. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/pion/dtls/v2: affected <= 2.2.12
- Go github.com/pion/dtls/v3: affected >= 3.1.0, <= 3.1.0; < 3.0.11; fixed in 3.0.11, 3.1.1
- Go github.com/pion/dtls: affected <= 1.5.4

## Suggested inspection (read-only)
- Go github.com/pion/dtls/v2: check the installed version with your package manager.
- Go github.com/pion/dtls/v3: check the installed version with your package manager.
- Go github.com/pion/dtls: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/pion/dtls/v2, github.com/pion/dtls/v3, github.com/pion/dtls.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-9f3f-wv7r-qc8r (GitHub-reviewed advisory GHSA-9f3f-wv7r-qc8r lists affected ranges: Go github.com/pion/dtls/v2 >=0 =0 =3.1.0 =0 <3.0.11)

Commands are suggestions: review each one before running it.