CVE-2026-54908

CVE-2026-54908 is a medium-severity out-of-bounds read vulnerability in github.com/pion/dtls/v3 (go), affecting versions <= 3.1.2. It is fixed in 3.1.4.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Pion DTLS vulnerable to denial of service via panic while parsing a crafted ECDHE_PSK ServerKeyExchange message

Workarounds

No work around; please upgrade to v3.1.4 or a newer version.

Impact

Remote denial of service via panic while parsing a crafted ECDHE_PSK ServerKeyExchange message.

A read operation accesses a memory location beyond the intended buffer boundary. Typical impact: sensitive data disclosure or crash.

Affected versions

github.com/pion/dtls/v3 (<= 3.1.2)

Security releases

github.com/pion/dtls/v3 → 3.1.4 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade to v3.1.4 or later. This version includes this patch https://github.com/pion/dtls/pull/839 which fixes the issue.

Frequently Asked Questions

  1. What is CVE-2026-54908? CVE-2026-54908 is a medium-severity out-of-bounds read vulnerability in github.com/pion/dtls/v3 (go), affecting versions <= 3.1.2. It is fixed in 3.1.4. A read operation accesses a memory location beyond the intended buffer boundary.
  2. Which versions of github.com/pion/dtls/v3 are affected by CVE-2026-54908? github.com/pion/dtls/v3 (go) versions <= 3.1.2 is affected.
  3. Is there a fix for CVE-2026-54908? Yes. CVE-2026-54908 is fixed in 3.1.4. Upgrade to this version or later.
  4. Is CVE-2026-54908 exploitable, and should I be worried? Whether CVE-2026-54908 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  5. What actually determines whether CVE-2026-54908 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  6. How do I fix CVE-2026-54908? Upgrade github.com/pion/dtls/v3 to 3.1.4 or later.

Other vulnerabilities in github.com/pion/dtls/v3

Stop the waste.
Protect your environment with Kodem.