Is github.com/pion/dtls/v2 2.2 vulnerable?
Go · 13 releases from 2.2.0 to 2.2.12 · latest github.com/pion/dtls/v2 is 2.2.12 · checked 18 Nov 2026
Yes: 2 known advisories
Yes. github.com/pion/dtls/v2 2.2.12, the last 2.2 release, is affected by 2 known security advisories (1 medium, 1 low), including CVE-2026-26014, CVE-2026-26014. 4 more affect earlier 2.2.x releases. At least one has no fixed release yet.
Is your project on an affected github.com/pion/dtls/v2?
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/v2 2.2.12
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
- <=2.2.12
- Fixed in
- No fix released
Fixed within 2.2.x, affecting earlier releases
Panic during unmarshal of Server Hello in github.com/pion/dtls/v2
- Affected
- <2.2.4
- Fixed in
- 2.2.4
Panic during unmarshal of Hello Verify Request in github.com/pion/dtls/v2
- Affected
- <2.2.4
- Fixed in
- 2.2.4
Panic during unmarshal of Hello Verify Request in github.com/pion/dtls/v2
- Affected
- <2.2.4
- Fixed in
- 2.2.4
Panic during unmarshal of Hello Verify Request in github.com/pion/dtls/v2
- Affected
- <2.2.4
- Fixed in
- 2.2.4
Every github.com/pion/dtls/v2 2.2.x release
Affected: 2.2.0 to 2.2.12.
| Version | Known advisories |
|---|---|
| github.com/pion/dtls/v2 2.2.12 | CVE-2026-26014, CVE-2026-26014 |
| github.com/pion/dtls/v2 2.2.11 | CVE-2026-26014, CVE-2026-26014 |
| github.com/pion/dtls/v2 2.2.10 | CVE-2026-26014, CVE-2026-26014 |
| github.com/pion/dtls/v2 2.2.9 | CVE-2026-26014, CVE-2026-26014 |
| github.com/pion/dtls/v2 2.2.8 | CVE-2026-26014, CVE-2026-26014 |
| github.com/pion/dtls/v2 2.2.7 | CVE-2026-26014, CVE-2026-26014 |
| github.com/pion/dtls/v2 2.2.6 | CVE-2026-26014, CVE-2026-26014 |
| github.com/pion/dtls/v2 2.2.5 | CVE-2026-26014, CVE-2026-26014 |
| github.com/pion/dtls/v2 2.2.4 | CVE-2026-26014, CVE-2026-26014 |
| github.com/pion/dtls/v2 2.2.3 | CVE-2026-26014, CVE-2026-26014, GO-2023-1535, GO-2023-1534, GHSA-4xgv-j62q-h3rj, GHSA-hxp2-xqf3-v83h |
| github.com/pion/dtls/v2 2.2.2 | CVE-2026-26014, CVE-2026-26014, GO-2023-1535, GO-2023-1534, GHSA-4xgv-j62q-h3rj, GHSA-hxp2-xqf3-v83h |
| github.com/pion/dtls/v2 2.2.1 | CVE-2026-26014, CVE-2026-26014, GO-2023-1535, GO-2023-1534, GHSA-4xgv-j62q-h3rj, GHSA-hxp2-xqf3-v83h |
| github.com/pion/dtls/v2 2.2.0 | CVE-2026-26014, CVE-2026-26014, GO-2023-1535, GO-2023-1534, GHSA-4xgv-j62q-h3rj, GHSA-hxp2-xqf3-v83h |
Which of your client projects are still on github.com/pion/dtls/v2 2.2?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/pion/dtls/v2 version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/pion/dtls/v2 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.