cve.bz

CVE-2026-26014 pion dtls

5.9 mediumEPSS 0.7%Fix available

Medium (5.9) in pion dtls. EPSS 0.7% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/pion/dtls/v3 3.0.11, 3.1.1.

On this page
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.

Severity

CVSS 3.1

5.9 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.7% (unchanged from 0.7% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 54th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-02-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-26014 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-26014?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-26014?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-26014 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
pion:dtlsbefore 3.1.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-9f3f-wv7r-qc8rGogithub.com/pion/dtls/v3>=3.1.0 <3.1.13.1.1
GHSA-9f3f-wv7r-qc8rGogithub.com/pion/dtls/v2<=2.2.12no fix published
GHSA-9f3f-wv7r-qc8rGogithub.com/pion/dtls<=1.5.4no fix published
GHSA-9f3f-wv7r-qc8rGogithub.com/pion/dtls/v3<3.0.113.0.11
GO-2026-4479Gogithub.com/pion/dtlsall versionsno fix published
GO-2026-4479Gogithub.com/pion/dtls/v2all versionsno fix published
GO-2026-4479Gogithub.com/pion/dtls/v3>=3.0.10 <3.0.11
>=3.1.0 <3.1.1
3.0.11, 3.1.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14golang-github-pion-dtls.v2no fix listedDEBIAN-CVE-2026-26014
Debian14golang-github-pion-dtls-v33.1.2-1DEBIAN-CVE-2026-26014
Ubuntu24.04:LTS, 25.10golang-github-pion-dtls.v2no fix listedUBUNTU-CVE-2026-26014
Ubuntu26.04:LTS, 26.10golang-github-pion-dtls-v3, golang-github-pion-dtls.v2no fix listedUBUNTU-CVE-2026-26014
openSUSELeap 15.6govulncheck-vulndb0.0.20260226T182644-150000.1.149.1SUSE-SU-2026:0757-1
openSUSELeap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-1
Azure Linux2telegraf1.29.4-21AZL-77645
Azure Linux3telegraf1.31.0-15AZL-77649

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

Red Hat Product Security classified this issue as Moderate severity, because an unauthenticated remote attacker could, in theory, take advantage of the improper nonce generation in Pion DTLS to more easily obtain the authentication key for AES-GCM ciphers and spoof or manipulate DTLS traffic. However, exploitation requires specific conditions and a detailed understanding of the protocol, contributing to a higher attack complexity. Additionally, there is no direct effect on data integrity or availability solely from this issue, and successful exploitation typically requires carefully crafted, protocol-level interactions. These factors limit the practical risk in most real-world deployments.

Red Hat's mitigation

No mitigation is currently available that meets Red Hat Product Security’s standards for usability, deployment, applicability, or stability.

ProductPackageStateAdvisory
Network Observability Operatornetwork-observability/network-observability-ebpf-agent-rhel9Fix deferred
Network Observability Operatornetwork-observability/network-observability-flowlogs-pipeline-rhel9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-26014.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).

References

Check your stackJSON