Vulnerability Database · Go · Package report

github.com/pion/dtls: vulnerability history, versions and safety

github.com/pion/dtls is a package in the Go ecosystem. Vulert records 9 vulnerabilities for it across 98 releases, from Apr 2021 to Feb 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
9 vulnerabilities recorded C1 H1 M4 U3
i
3 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 19 Feb 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on github.com/pion/dtls v1.5.4 i

Updated on 23 Oct 2026

Careful: v1.5.4 has 9 known vulnerabilities, and 3 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Widely used
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release v1.5.4 — affected i
  • Vulnerabilities on record 9 over 4 years · 1 in the last year i
  • Latest disclosure 19 Feb 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 3 i
  • Stars 705 i
  • OpenSSF scorecard 5/10 i
  • Last release 83 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for github.com/pion/dtls, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v1.5.4-0.20191112225421-0649d6e970ce 12 Nov 2019 C1 H1 M4 U3 MIT No Details →
v1.5.5-0.20191112225421-0649d6e970ce 12 Nov 2019 C1 H1 M4 U3 MIT No Details →
v1.5.4 10 Nov 2019 C1 H1 M4 U3 MIT No Details →
v1.5.4-0.20191110084921-d0f3d4c64ee6 10 Nov 2019 C1 H1 M4 U3 MIT No Details →
v1.5.4-0.20191107060743-589dc6eb1601 07 Nov 2019 C1 H1 M4 U3 MIT No Details →
v1.5.4-0.20191105072917-6f0da2597d9a 05 Nov 2019 C1 H1 M4 U3 MIT No Details →
v1.5.4-0.20191105072917-77fae27e533b 05 Nov 2019 C1 H1 M4 U3 MIT No Details →
v1.5.4-0.20191105072917-f5d7d3e09c1f 05 Nov 2019 C1 H1 M4 U3 MIT No Details →
v1.5.4-0.20191105072910-ef6e5315aff0 05 Nov 2019 C1 H1 M4 U3 MIT No Details →
v1.5.4-0.20191101005546-61dd7c278aa6 01 Nov 2019 C1 H1 M4 U3 MIT No Details →
v1.5.4-0.20191030072855-2f60c8800521 30 Oct 2019 C1 H1 M4 U3 MIT No Details →
v1.5.3 29 Oct 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2 11 Oct 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20191001193209-82948855ecb8 01 Oct 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20191001192655-ef026b5574c0 01 Oct 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20191001171303-83f576bd9d46 01 Oct 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20190929184459-a814dd1884b4 29 Sep 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20190929175457-52d8414e36a0 29 Sep 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20190929175220-4b2ff17ea31a 29 Sep 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20190929174644-96af336a6799 29 Sep 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20190929174644-a814b18d20e2 29 Sep 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20190915000208-e4481fc3379a 15 Sep 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20190904065433-5f9fe5fa7544 04 Sep 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20190903225920-921347ec390f 03 Sep 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20190902042437-b5f6b5eb8954 02 Sep 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20190831135441-d67aa57e2033 31 Aug 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20190831072325-16d7d042a33c 31 Aug 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20190829043156-0e96d7151883 29 Aug 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20190829043156-5a95192eee18 29 Aug 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20190829043156-c1f28ad1cbd5 29 Aug 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20190829041040-a0a80f78578c 29 Aug 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20190827072807-02c03cb85fc1 27 Aug 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20190827072807-d655bd90de48 27 Aug 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20190827072807-e8e0eb34d94e 27 Aug 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20190827055950-a96512aa9897 27 Aug 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20190827054516-4d033bdd7481 27 Aug 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20190827054516-a3ca587ab2c9 27 Aug 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20190827053746-fc9293fd6e48 27 Aug 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20190827052029-48de3bde1ce2 27 Aug 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20190827011300-373a404464a2 27 Aug 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20190826203604-04dad24a729f 26 Aug 2019 C1 H1 M4 U3 MIT No Details →
v0.0.0-20190826173905-b28063ed43f5 26 Aug 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20190826173905-b28063ed43f5 26 Aug 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20190824234022-56a964a0a9fc 24 Aug 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20190823224048-b895f9c55948 23 Aug 2019 C1 H1 M4 U3 MIT No Details →
v1.5.2-0.20190823010630-d2b0e43e8a66 23 Aug 2019 C1 H1 M4 U3 MIT No Details →
v1.5.1 14 Aug 2019 C1 H1 M4 U3 MIT No Details →
v1.5.1-0.20190805141725-3712d17a6203 05 Aug 2019 C1 H1 M4 U3 MIT No Details →
v1.5.1-0.20190802053221-fa63c5c88ad4 02 Aug 2019 C1 H1 M4 U3 MIT No Details →
v1.5.1-0.20190802053200-9e07f99920ed 02 Aug 2019 C1 H1 M4 U3 MIT No Details →
v1.5.1-0.20190801200913-bf2f21a1df49 01 Aug 2019 C1 H1 M4 U3 MIT No Details →
v1.4.1-0.20190726083350-1c1d9fc46e30 26 Jul 2019 C1 H1 M4 U3 MIT No Details →
v1.4.1-0.20190726083350-c7f9d8404cb3 26 Jul 2019 C1 H1 M4 U3 MIT No Details →
v1.5.0 26 Jul 2019 C1 H1 M4 U3 MIT No Details →
v1.4.0 04 Jul 2019 C1 H1 M4 U3 MIT No Details →
v1.3.6-0.20190704092512-506d54770b56 04 Jul 2019 C1 H1 M4 U3 MIT No Details →
v1.3.6-0.20190704092512-99cc851ebe41 04 Jul 2019 C1 H1 M4 U3 MIT No Details →
v1.3.6-0.20190704092512-e150ca7c582c 04 Jul 2019 C1 H1 M4 U3 MIT No Details →
v1.3.6-0.20190702184345-080adbc6d06d 02 Jul 2019 C1 H1 M4 U3 MIT No Details →
v1.3.6-0.20190702184345-1281f1ebe7ca 02 Jul 2019 C1 H1 M4 U3 MIT No Details →
v1.3.6-0.20190702184345-1adc419247d3 02 Jul 2019 C1 H1 M4 U3 MIT No Details →
v1.3.6-0.20190702184345-1b36749ff234 02 Jul 2019 C1 H1 M4 U3 MIT No Details →
v1.3.6-0.20190702184345-79cd91703755 02 Jul 2019 C1 H1 M4 U3 MIT No Details →
v1.3.6-0.20190702184345-bdae00800472 02 Jul 2019 C1 H1 M4 U3 MIT No Details →
v1.3.6-0.20190702184345-f5ceadd294b4 02 Jul 2019 C1 H1 M4 U3 MIT No Details →
v1.3.6-0.20190601083948-b1c2af308c30 01 Jun 2019 C1 H1 M4 U3 MIT No Details →
v1.3.6-0.20190524230941-89f698cfe3ac 24 May 2019 C1 H1 M4 U3 MIT No Details →
v1.3.6-0.20190524220002-2a5695eda53b 24 May 2019 C1 H1 M4 U3 MIT No Details →
v1.3.6-0.20190524220002-6830e2f80005 24 May 2019 C1 H1 M4 U3 MIT No Details →
v1.3.6-0.20190524215946-977d56b70820 24 May 2019 C1 H1 M4 U3 MIT No Details →
v1.3.6-0.20190524210747-d864f9930fec 24 May 2019 C1 H1 M4 U3 MIT No Details →
v1.3.6-0.20190524210118-ebb3cbdfd8b7 24 May 2019 C1 H1 M4 U3 MIT No Details →
v1.3.5 24 May 2019 C1 H1 M4 U3 MIT No Details →
v1.3.5-0.20190524185138-4e617446e2c4 24 May 2019 C1 H1 M4 U3 MIT No Details →
v1.3.5-0.20190524185138-fcc2cfd098bb 24 May 2019 C1 H1 M4 U3 MIT No Details →
v1.3.5-0.20190523085450-a2d36ed05c60 23 May 2019 C1 H1 M4 U3 MIT No Details →
v1.3.5-0.20190523085450-bb439befbe60 23 May 2019 C1 H1 M4 U3 MIT No Details →
v1.3.5-0.20190523071827-b0ae3333b83e 23 May 2019 C1 H1 M4 U3 MIT No Details →
v1.3.5-0.20190523070850-1f6822ac4d23 23 May 2019 C1 H1 M4 U3 MIT No Details →
v1.3.5-0.20190519005646-9f90a4dd5c8a 19 May 2019 C1 H1 M4 U3 MIT No Details →
v1.3.4 07 May 2019 C1 H1 M4 U3 MIT No Details →
v1.3.4-0.20190424075135-8135837be171 24 Apr 2019 C1 H1 M4 U3 MIT No Details →
v1.3.4-0.20190421032102-f7665b9506bf 21 Apr 2019 C1 H1 M4 U3 MIT No Details →
v1.3.4-0.20190412103029-035a26f794f3 12 Apr 2019 C1 H1 M4 U3 MIT No Details →
v1.3.3 12 Apr 2019 C1 H1 M4 U3 MIT No Details →
v1.3.2 09 Apr 2019 C1 H1 M4 U3 MIT No Details →
v1.3.1 09 Apr 2019 C1 H1 M4 U3 MIT No Details →
v1.3.0 06 Apr 2019 C1 H1 M4 U3 MIT No Details →
v1.2.4-0.20190406091950-59da19993d66 06 Apr 2019 C1 H1 M4 U3 MIT No Details →
v1.2.4-0.20190406010909-f365b82f4a96 06 Apr 2019 C1 H1 M4 U3 MIT No Details →
v1.2.3 04 Apr 2019 C1 H1 M4 U3 MIT No Details →
v1.0.3-0.20181222160605-da12df742155 22 Dec 2018 C1 H1 M4 U3 MIT No Details →
v1.0.2 19 Dec 2018 C1 H1 M4 U3 MIT No Details →
v1.0.2-0.20181219055838-4552d8aa107a 19 Dec 2018 C1 H1 M4 U3 MIT No Details →
v1.0.2-0.20181219040558-400d5abde1b9 19 Dec 2018 C1 H1 M4 U3 MIT No Details →
v1.0.2-0.20181213004052-d0dd5a2f6c2d 13 Dec 2018 C1 H1 M4 U3 MIT No Details →
v1.0.1 04 Dec 2018 C1 H1 M4 U3 — No Details →
v1.0.0 03 Dec 2018 C1 H1 M4 U3 — No Details →

All 98 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 3
  • 2022 3
  • 2023 2
  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 9 were recorded in the last 12 months.

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/pion/dtls

Is github.com/pion/dtls safe to use?

Vulert records 9 vulnerabilities for github.com/pion/dtls in Go: 1 critical, 1 high, 4 medium and 0 low, plus 3 not yet rated. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is github.com/pion/dtls's Vulert package health score?

Vulert scores github.com/pion/dtls 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of github.com/pion/dtls affected?

Yes. v1.5.4, the version you would install today, has 9 known vulnerabilities, and 3 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of github.com/pion/dtls should I use?

v1.5.4 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does github.com/pion/dtls have?

9 vulnerabilities are recorded for github.com/pion/dtls in the Go ecosystem: 1 critical, 1 high, 4 medium and 0 low, plus 3 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/pion/dtls vulnerabilities disclosed?

1 vulnerability was recorded for github.com/pion/dtls in the last 12 months, and the oldest entry in this database dates to 14 Apr 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of github.com/pion/dtls are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor github.com/pion/dtls for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/pion/dtls version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.