# CVE-2026-26014: GO-2026-4479 - Usage of random nonce generation with AES GCM ciphers risks leaking the authentication key in github.com/pion/dtls

Source: https://junglewise.ai/threats/cve-2026-26014-pion-dtls-s-usage-of-random-nonce-generation-with-aes-gcm-ciphers  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-02-19  
License: CC BY 4.0 with a link back

CVE-2026-26014 · Severity: low · CVSS 3.1 · Published 2026-02-19

Usage of random nonce generation with AES GCM ciphers risks leaking the authentication key in github.com/pion/dtls

Technologies: [github.com/pion/dtls (Go)](https://junglewise.ai/threats/technologies/github-com-pion-dtls), [github.com/pion/dtls/v2 (Go)](https://junglewise.ai/threats/technologies/github-com-pion-dtls-v2). Vendors: [Go](https://junglewise.ai/threats/vendors/go).

## Quick answers

**Is CVE-2026-26014 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-26014 being exploited in the wild.

**How severe is CVE-2026-26014?** Low severity, with a CVSS score of 3.1, published 19 February 2026.

**Which products and versions are affected?** github.com/pion/dtls (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.5.4; github.com/pion/dtls/v2 (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=2.2.12; github.com/pion/dtls/v3 (Go) SEMVER:introduced=3.0.10,fixed=3.0.11,introduced=3.1.0,fixed=3.1.1, SEMVER:introduced=3.1.0,fixed=3.1.1.

**Is there a fix for CVE-2026-26014?** Yes. github.com/pion/dtls/v3 (Go): upgrade to 3.1.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2026-26014?** Check whether you run github.com/pion/dtls (Go), github.com/pion/dtls/v2 (Go) or github.com/pion/dtls/v3 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/pion/dtls/v3 (Go): upgrade to 3.1.1 or later

  ```sh
  go get github.com/pion/dtls/v3@v3.1.1
  ```


## Affected products

- github.com/pion/dtls (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.5.4
- github.com/pion/dtls/v2 (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=2.2.12
- github.com/pion/dtls/v3 (Go) SEMVER:introduced=3.0.10,fixed=3.0.11,introduced=3.1.0,fixed=3.1.1, SEMVER:introduced=3.1.0,fixed=3.1.1

## Identifiers

- CVE-2026-26014
- GHSA-9f3f-wv7r-qc8r
- GO-2026-4479

## Related threats

- [Pion DTLS denial of service via panic in ServerKeyExchange parsing](https://junglewise.ai/threats/cve-2026-54908-pion-dtls-denial-of-service-via-panic-in-serverkeyexchange)
- [GO-2023-1535 - Panic during unmarshal of Server Hello in github.com/pion/dtls/v2](https://junglewise.ai/threats/go-2023-1535-panic-during-unmarshal-of-server-hello-in-github-com-pion-59d59d2d)
- [GO-2023-1534 - Panic during unmarshal of Hello Verify Request in github.com/pion/dtls/v2](https://junglewise.ai/threats/go-2023-1534-panic-during-unmarshal-of-hello-verify-request-in-github-2da81b22)
- [Panic during unmarshal of Hello Verify Request in github.com/pion/dtls/v2](https://junglewise.ai/threats/panic-during-unmarshal-of-hello-verify-request-in-github-com-pion-dtls-c23b7d58)
- [Panic during unmarshal of Hello Verify Request in github.com/pion/dtls/v2](https://junglewise.ai/threats/panic-during-unmarshal-of-hello-verify-request-in-github-com-pion-dtls-20a8f61b)