CVE-2026-54908

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 56% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Pion DTLS is a Go implementation of Datagram Transport Layer Security. Versions prior to 3.1.4 are vulnerable to Remote Denial of Service via panic while parsing a crafted ECDHE_PSK ServerKeyExchange message. This issue has been fixed in version 3.1.4.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
33
EG Risk 33/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity63% × 45%
Exploitation1% × 40%
Automatability30% × 15%
EPSS PROB
0.5%
EPSS %ILE
43rd
KEV
Not listed

Published

July 1, 2026

Last Modified

July 2, 2026

Advisory Details (2)

Auto-updated Jul 3, 2026
Patch available. Sources: github, github_pr.
githubMentions a patch (unverified)

Denial of service via panic while parsing a crafted ECDHE_PSK ServerKeyExchange message · Advisory · pion/dtls · GitHub

https://github.com/pion/dtls/security/advisories/GHSA-wg4g-wm44-ch5j
github_pr Patch Available

Fix panic unmarshaling ECDHE_PSK ServerKeyExchange

Patch available: pion/dtls v3.1.3 (PR #839 merged 2026-06-02)

https://github.com/pion/dtls/pull/839

Vendor Advisories for CVE-2026-54908(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(5 across 4 ecosystems)
Debian:14(2)
PackageVulnerable rangeFix by version rangeDependents
golang-github-pion-dtls.v22.2.6-1, 2.2.6-2
  • every version on: no fix on record
—
golang-github-pion-dtls-v33.0.7-1, 3.0.7-2, 3.1.2-1, 3.1.5-1
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-pion-dtls.v22.2.6-1, 2.2.6-2
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-pion-dtls.v22.2.6-1, 2.2.6-2
  • every version on: no fix on record
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/pion/dtls/v3—
  • every version up to 3.1.4: fixed in 3.1.4
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 33× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 166 total refreshes for this CVE.

  1. 2026-10-10 20:00 UTCEPSS rescore
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-08 17:12 UTCEPSS rescore
  4. 2026-10-07 23:48 UTCEPSS rescore
  5. 2026-10-06 15:18 UTCEPSS rescore
  6. 2026-10-05 17:43 UTCEPSS rescore
  7. 2026-10-04 23:22 UTCEPSS rescore
  8. 2026-10-03 14:26 UTCEPSS rescore
  9. 2026-10-02 17:56 UTCEPSS rescore
  10. 2026-10-01 19:50 UTCEPSS rescore
  11. 2026-09-30 15:03 UTCEPSS rescore
  12. 2026-09-29 15:22 UTCEPSS rescore
  13. 2026-09-28 13:51 UTCEPSS rescore
  14. 2026-09-27 13:48 UTCEPSS rescore
  15. 2026-09-26 15:59 UTCEPSS rescore
  16. 2026-09-24 14:04 UTCEPSS rescore
  17. 2026-09-23 17:54 UTCEPSS rescore
  18. 2026-09-23 06:49 UTCEG score recompute
  19. 2026-09-23 06:49 UTCVendor advisory
  20. 2026-09-20 20:16 UTCEPSS rescore
  21. 2026-09-18 19:28 UTCEPSS rescore
  22. 2026-09-18 06:28 UTCEG score recompute
  23. 2026-09-18 06:28 UTCVendor advisory
  24. 2026-09-17 19:31 UTCEPSS rescore
  25. 2026-09-16 14:08 UTCEPSS rescore
Show 75 more
  1. 2026-09-16 05:15 UTCEPSS rescore
  2. 2026-09-15 03:11 UTCEPSS rescore
  3. 2026-09-14 00:21 UTCEG score recompute
  4. 2026-09-14 00:21 UTCVendor advisory
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-12 14:37 UTCEG score recompute
  7. 2026-09-12 14:37 UTCVendor advisory
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-10 09:35 UTCEPSS rescore
  10. 2026-09-08 22:01 UTCEPSS rescore
  11. 2026-09-07 16:01 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-06 00:45 UTCEG score recompute
  14. 2026-09-06 00:45 UTCVendor advisory
  15. 2026-09-04 05:06 UTCEPSS rescore
  16. 2026-09-02 14:12 UTCEPSS rescore
  17. 2026-09-01 13:54 UTCEPSS rescore
  18. 2026-09-01 04:40 UTCEPSS rescore
  19. 2026-08-30 19:17 UTCEPSS rescore
  20. 2026-08-30 11:43 UTCEG score recompute
  21. 2026-08-30 11:43 UTCVendor advisory
  22. 2026-08-30 01:22 UTCEPSS rescore
  23. 2026-08-28 21:41 UTCEPSS rescore
  24. 2026-08-27 22:24 UTCEG score recompute
  25. 2026-08-27 22:24 UTCVendor advisory
  26. 2026-08-27 14:25 UTCEPSS rescore
  27. 2026-08-26 14:46 UTCEPSS rescore
  28. 2026-08-25 16:16 UTCEG score recompute
  29. 2026-08-25 16:16 UTCVendor advisory
  30. 2026-08-25 13:49 UTCEPSS rescore
  31. 2026-08-24 12:38 UTCEG score recompute
  32. 2026-08-24 12:38 UTCVendor advisory
  33. 2026-08-23 10:29 UTCEG score recompute
  34. 2026-08-23 10:29 UTCVendor advisory
  35. 2026-08-23 00:19 UTCEPSS rescore
  36. 2026-08-22 08:32 UTCEG score recompute
  37. 2026-08-22 08:32 UTCVendor advisory
  38. 2026-08-21 23:49 UTCEPSS rescore
  39. 2026-08-21 06:34 UTCEG score recompute
  40. 2026-08-21 06:34 UTCVendor advisory
  41. 2026-08-20 22:55 UTCEPSS rescore
  42. 2026-08-20 04:36 UTCEG score recompute
  43. 2026-08-19 17:04 UTCEPSS rescore
  44. 2026-08-18 20:57 UTCEG score recompute
  45. 2026-08-18 20:57 UTCVendor advisory
  46. 2026-08-18 13:48 UTCEPSS rescore
  47. 2026-08-17 13:47 UTCEPSS rescore
  48. 2026-08-17 09:25 UTCEG score recompute
  49. 2026-08-17 09:25 UTCVendor advisory
  50. 2026-08-16 14:56 UTCEPSS rescore
  51. 2026-08-16 07:27 UTCEG score recompute
  52. 2026-08-16 07:27 UTCVendor advisory
  53. 2026-08-16 02:14 UTCEPSS rescore
  54. 2026-08-15 05:30 UTCEG score recompute
  55. 2026-08-15 05:30 UTCVendor advisory
  56. 2026-08-15 01:30 UTCEPSS rescore
  57. 2026-08-14 03:32 UTCEG score recompute
  58. 2026-08-14 03:32 UTCVendor advisory
  59. 2026-08-13 22:00 UTCEPSS rescore
  60. 2026-08-13 01:34 UTCEG score recompute
  61. 2026-08-12 13:51 UTCEPSS rescore
  62. 2026-08-11 23:36 UTCEG score recompute
  63. 2026-08-11 23:36 UTCVendor advisory
  64. 2026-08-11 00:00 UTCEPSS rescore
  65. 2026-08-09 19:41 UTCEG score recompute
  66. 2026-08-09 13:46 UTCEPSS rescore
  67. 2026-08-08 17:44 UTCEG score recompute
  68. 2026-08-08 17:44 UTCVendor advisory
  69. 2026-08-08 16:37 UTCEPSS rescore
  70. 2026-08-07 15:46 UTCVendor advisory
  71. 2026-08-06 13:49 UTCEG score recompute
  72. 2026-08-06 13:49 UTCVendor advisory
  73. 2026-08-06 13:47 UTCEPSS rescore
  74. 2026-08-05 19:17 UTCEPSS rescore
  75. 2026-08-05 11:42 UTCEG score recompute

Related CVEs(same product + same CWE)

Same product

1 shown

Debian:12:golang-github-pion-dtls.v2

Frequently asked(5)

What is CVE-2026-54908?
CVE-2026-54908 is a medium vulnerability published on July 1, 2026. Pion DTLS is a Go implementation of Datagram Transport Layer Security. Versions prior to 3.1.4 are vulnerable to Remote Denial of Service via panic while parsing a crafted ECDHE_PSK ServerKeyExchange message. This issue has been fixed in version 3.1.4.
When was CVE-2026-54908 disclosed?
CVE-2026-54908 was first published on July 1, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54908 actively exploited?
CVE-2026-54908 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54908?
CVE-2026-54908 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54908?
A fix for CVE-2026-54908 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54908 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54908

Explore →

Is Your Infrastructure Affected by CVE-2026-54908?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs