Skip to content
Fencer Intel
medium 5.9

CVE-2026-26014 json

Pion DTLS uses random nonce generation with AES GCM ciphers risks leaking the authentication key

published 8mo ago modified last mo. also EUVD-2026-6169 , GHSA-9f3f-wv7r-qc8r , GO-2026-4479

cvss
5.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 52%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/pion/dtls/v3 3.0.11, 3.1.1
  • pion dtls 3.0.11, 3.1.1
  • golang-github-pion-dtls-v3 Debian 14 3.1.2-1

debian advisories DEBIAN-CVE-2026-26014

  • govulncheck-vulndb openSUSE Leap 15.6 0.0.20260226T182644-150000.1.149.1

suse advisories SUSE-SU-2026:0757-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

  • telegraf CBL-Mariner 2.0 1.29.4-21
  • telegraf Azure Linux 3.0 1.31.0-15

azure linux advisories AZL-77645AZL-77649

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Is CVE-2026-26014 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-26014 updated cvss 5.9

github.com/pion/dtls: Pion DTLS uses random nonce generation with AES GCM ciphers risks leaking the authentication key

  • Red Hat Network Observability Operator network-observability/network-observability-ebpf-agent-rhel9, network-observability/network-observability-flowlogs-pipeline-rhel9
    affected: workaround, no fix available “No mitigation is currently available that meets Red Hat Product Security’s standards for usability, deployment, applicability, or stability.”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
8mo ago

Exploit prediction

0.69% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
GitHub 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/pion/dtls/v3
>=3.1.0, <3.1.1
<3.0.11
>=3.0.10, <3.0.11
3.1.1
3.0.11
go github.com/pion/dtls/v2
<=2.2.12
all versions
 no fix listed
go github.com/pion/dtls
<=1.5.4
all versions
 no fix listed

Affected products

  • pion dtls

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.