How severe is CVE-2026-26014?

CVE-2026-26014 has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2026-26014?

CVE-2026-26014 affects the following packages: github.com/pion/dtls/v3 (Go), github.com/pion/dtls/v2 (Go), github.com/pion/dtls (Go), github.com/pion/dtls/v3 (Go). Ecosystems affected: Go.

How do I fix CVE-2026-26014?

Update github.com/pion/dtls/v3 to 3.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-26014 is resolved across your whole dependency graph.

How do I detect CVE-2026-26014 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/pion/dtls/v3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-26014 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2026-26014 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-26014 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-26014?

CVE-2026-26014 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 53th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-26014?

CVE-2026-26014 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-26014 published, and has it been updated?

CVE-2026-26014 was published on February 11, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

MEDIUM severity

CVE-2026-26014 — dtls

MEDIUMFix: pion/dtls@61762de

CVE-2026-26014 is a medium-severity (CVSS 5.9) Information Exposure vulnerability in github.com/pion/dtls/v3. A fix is available for github.com/pion/dtls/v3 — see the affected versions and patch details below.

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

Also known asGHSA-9f3f-wv7r-qc8rGO-2026-4479

Published

Feb 11, 2026

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

2 / 4

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-26014.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk-0.01%

Lower risk than most CVEs53th percentile — riskier than 53% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

🐹github.com/pion/dtls/v3🐹github.com/pion/dtls/v2🐹github.com/pion/dtls🐹github.com/pion/dtls/v3

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

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

Affected Packages

4 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/pion/dtls/v3`	≥ 3.1.0&&< 3.1.1	3.1.1`go get github.com/pion/dtls/v3@v3.1.1`
🐹Go	`github.com/pion/dtls/v2`	all versions	No fix
🐹Go	`github.com/pion/dtls`	all versions	No fix
🐹Go	`github.com/pion/dtls/v3`	all versions	3.0.11`go get github.com/pion/dtls/v3@v3.0.11`

Affected Products

1 product · 1 configurations

Application

dtlspion

< 3.1.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/pion/dtls/v3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/pion/dtls/v3 to 3.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-26014 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

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…

Workaround published by Red Hat

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

Source: Red Hat security advisory for CVE-2026-26014 (CC BY 4.0)

Frequently Asked Questions

### 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](https://www.rfc-editor.org/rfc/rfc9325#section-7.2.1). v3.0.11 is a backport patch supporti