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.
CVE-2026-54908
This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 76% 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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(medium)
- EG Risk
- 33(Track)EG Risk 33/100SSVC: Track
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 computedSeverity63% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 24.3%
- KEV
- Not listed
Published
July 1, 2026
Last Modified
July 2, 2026
Advisory Details (2)
Auto-updated Jul 3, 2026Denial 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-ch5jFix panic unmarshaling ECDHE_PSK ServerKeyExchange
Patch available: pion/dtls v3.1.3 (PR #839 merged 2026-06-02)
https://github.com/pion/dtls/pull/839Vendor Advisories for CVE-2026-54908(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 40× 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.
- 2026-07-23 03:20 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 00:49 UTCVendor advisory
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-15 22:51 UTCVendor advisory
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 20:53 UTCVendor advisory
- 2026-07-13 22:31 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 16:57 UTCVendor advisory
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 14:59 UTCVendor advisory
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
Show 15 moreShow fewer
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-01 21:08 UTCEG score recompute
- 2026-07-01 21:08 UTCNVD updatefirst tracked
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
- CVE-2006-10003EG 9.8CRITICAL
- CVE-2015-20107NVD 7.6EG 9.8EPSS 94%HIGH
- CVE-2013-7381EG 9.8CRITICAL
- CVE-2014-0048EG 9.8EPSS 93%CRITICAL
- CVE-2007-4559EG 9.8EPSS 98%CRITICAL
- CVE-2013-3900NVD 5.5EG 9.0 KEVEPSS 99%MEDIUM
- CVE-2013-2094NVD 8.4EG 9.0 KEVEPSS 99%HIGH
- CVE-2014-9356EG 8.6EPSS 91%HIGH
- CVE-2014-5282EG 8.1HIGH
- CVE-2014-8141EG 7.8EPSS 94%HIGH
Same CWE
10 shownCWE-125
- CVE-2014-2898EG 9.8CRITICAL
- CVE-2014-2897EG 9.8CRITICAL
- CVE-2014-2896EG 9.8CRITICAL
- CVE-2015-9290EG 9.8CRITICAL
- CVE-2016-10749EG 9.8CRITICAL
- CVE-1999-0006EG 9.8EPSS 96%CRITICAL
- CVE-2014-3180EG 9.1CRITICAL
- CVE-2014-1508EG 9.1EPSS 90%CRITICAL
- CVE-2016-4523NVD 7.5EG 9.0 KEVEPSS 98%HIGH
- CVE-2016-1646NVD 8.8EG 9.0 KEVEPSS 99%HIGH
Frequently asked(5)
What is CVE-2026-54908?
When was CVE-2026-54908 disclosed?
Is CVE-2026-54908 actively exploited?
What is the CVSS score of CVE-2026-54908?
How do I remediate CVE-2026-54908?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-54908
Is Your Infrastructure Affected by CVE-2026-54908?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.