Out-of-Bounds Read in github.com/pion/dtls/v3 (CVE-2026-54908)
Summary
Vulnerability in github.com/pion/dtls/v3 (CVE-2026-54908). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.1.4 or later.
Original description
The description as published by the source.
In github.com/pion/dtls/v3 before 3.1.4, MessageServerKeyExchange.Unmarshal does not verify that data remains after parsing the PSK identity hint when handling ECDHE_PSK key exchange messages. A remote peer sending a crafted ServerKeyExchange message where the PSK hint consumes all remaining data triggers an index out of range runtime panic, causing a denial of service.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54908 has been found in github.com/pion/dtls/v3.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/pion/dtls/v3 to 3.1.4 or later.
If unsure, ask your IT team or search "github.com/pion/dtls/v3 CVE-2026-54908" on the vendor's site.
CVE-2026-54908 (github.com/pion/dtls/v3) — CWE-125
Patched: 3.1.4 — apply immediately
Workaround: No work around; please upgrade to v3.1.4 or a newer version.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Out-of-bounds read (CWE-125) exists in github.com/pion/dtls/v3.
Check the vendor advisory for the affected versions of github.com/pion/dtls/v3.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 3.1.4.
Workaround: No work around; please upgrade to v3.1.4 or a newer version.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/pion/dtls/v3' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/pion/dtls/v3' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/pion/dtls/v3を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
No work around; please upgrade to v3.1.4 or a newer version.パッチが適用されるまでの応急処置として、No work around; please upgrade to v3.1.4 or a newer version. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade github.com/pion/dtls/v3 to 3.1.4ステージング環境で 3.1.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-54908 golang-github-pion-dtls-v3
- Ubuntu UBUNTU-CVE-2026-54908 golang-github-pion-dtls.v2
References
- advisory github.com
- patch github.com
- patch github.com
- web nvd.nist.gov
- web github.com
- web github.com
- web github.com