Skip to main content
VulnerabilityPublished

CVE-2026-54908: pion dtls · Out-of-bounds Read

Affects pion dtlsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium : upgrade to 3.1.4 when convenient.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.1.4
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade dtls and github.com/pion/dtls to 3.1.4.

Affected software

ProductAffectedFixed in
piondtlsAffected
  • <3.1.4
Fixed in
  • 3.1.4
Gogithub.com/pion/dtlspkg:golang/github.com/pion/dtlsOther threatsAffected
  • <3.1.4
Fixed in
  • 3.1.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to pion dtls version 3.1.4 or later, which contains the official fix for this vulnerability. There are no workarounds available, so timely patching is required to prevent exploitation.

Description

CVE-2026-54908 is a medium severity vulnerability in the pion dtls library that causes a remote denial of service. The issue arises from an out-of-bounds read leading to a panic when parsing a specially crafted ECDHE_PSK ServerKeyExchange message. There is no workaround available; users must upgrade to version 3.1.4 or later to remediate this issue.

References

Community reviews

Loading reviews…