Is github.com/pion/dtls 1.5 vulnerable?
Go · 5 releases from 1.5.0 to 1.5.4 · latest github.com/pion/dtls is 1.5.4 · checked 18 Nov 2026
Yes: 7 known advisories
Yes. github.com/pion/dtls 1.5.4, the last 1.5 release, is affected by 7 known security advisories (1 high, 5 medium, 1 low), including CVE-2022-29190, CVE-2026-26014, CVE-2022-29222. 2 more affect earlier 1.5.x releases. At least one has no fixed release yet.
Is your project on an affected github.com/pion/dtls?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting github.com/pion/dtls 1.5.4
Usage of random nonce generation with AES GCM ciphers risks leaking the authentication key in github.com/pion/dtls
- Affected
- All versions
- Fixed in
- No fix released
Pion DTLS's usage of random nonce generation with AES GCM ciphers risks leaking the authentication key
- Affected
- <=1.5.4
- Fixed in
- No fix released
Panic during unmarshal of Hello Verify Request in github.com/pion/dtls/v2
- Affected
- <=1.5.4
- Fixed in
- No fix released
Panic during unmarshal of Hello Verify Request in github.com/pion/dtls/v2
- Affected
- <=1.5.4
- Fixed in
- No fix released
Pion/DLTS Accepts Client Certificates Without CertificateVerify
- Affected
- <2.1.5
- Fixed in
- 2.1.5
Pion DTLS Header reconstruction method can be thrown into an infinite loop
- Affected
- <2.1.4
- Fixed in
- 2.1.4
Pion/DTLS contains buffer for inbound DTLS fragments with no limit
- Affected
- <2.1.4
- Fixed in
- 2.1.4
Fixed within 1.5.x, affecting earlier releases
Improper Authenication in Pion DTLS
- Affected
- <1.5.2
- Fixed in
- 1.5.2
Improper authentication in github.com/pion/dtls
- Affected
- <1.5.2
- Fixed in
- 1.5.2
Every github.com/pion/dtls 1.5.x release
Affected: 1.5.0 to 1.5.4.
| Version | Known advisories |
|---|---|
| github.com/pion/dtls 1.5.4 | CVE-2026-26014, CVE-2026-26014, GHSA-4xgv-j62q-h3rj, GHSA-hxp2-xqf3-v83h, CVE-2022-29222, CVE-2022-29190, CVE-2022-29189 |
| github.com/pion/dtls 1.5.3 | CVE-2026-26014, CVE-2026-26014, GHSA-4xgv-j62q-h3rj, GHSA-hxp2-xqf3-v83h, CVE-2022-29222, CVE-2022-29190, CVE-2022-29189 |
| github.com/pion/dtls 1.5.2 | CVE-2026-26014, CVE-2026-26014, GHSA-4xgv-j62q-h3rj, GHSA-hxp2-xqf3-v83h, CVE-2022-29222, CVE-2022-29190, CVE-2022-29189 |
| github.com/pion/dtls 1.5.1 | CVE-2026-26014, CVE-2026-26014, GHSA-4xgv-j62q-h3rj, GHSA-hxp2-xqf3-v83h, CVE-2022-29222, CVE-2022-29190, CVE-2022-29189, CVE-2019-20786, CVE-2019-20786 |
| github.com/pion/dtls 1.5.0 | CVE-2026-26014, CVE-2026-26014, GHSA-4xgv-j62q-h3rj, GHSA-hxp2-xqf3-v83h, CVE-2022-29222, CVE-2022-29190, CVE-2022-29189, CVE-2019-20786, CVE-2019-20786 |
Which of your client projects are still on github.com/pion/dtls 1.5?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/pion/dtls version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/pion/dtls versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.