VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

websockets: vulnerability history, versions and safety

websockets is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 54 releases, from Jun 2018 to Jun 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H2 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all websockets vulnerabilities

Vulert verdict on websockets 17.3.0 i

Updated on 23 Oct 2026

Action needed: 17.3.0 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 86/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 17.3.0 — affected i
  • Vulnerabilities on record 4 over 2 years · 0 in the last year i
  • Latest disclosure 11 Jun 2021 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 32,995 packages i
  • Stars 5,736 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence BSD-3-Clause i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 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 websockets, 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
17.3.0 19 Oct 2026 U1 BSD-3-Clause Yes Details →
17.2.0 03 Oct 2026 U1 BSD-3-Clause Yes Details →
17.1.0 26 Aug 2026 U1 BSD-3-Clause Yes Details →
17.0.1 31 Jul 2026 U1 BSD-3-Clause Yes Details →
17.0.0 29 Jul 2026 U1 BSD-3-Clause Yes Details →
16.1.1 17 Jul 2026 U1 BSD-3-Clause Yes Details →
16.1.0 10 Jul 2026 U1 BSD-3-Clause Yes Details →
16.0.0 10 Jan 2026 U1 BSD-3-Clause Yes Details →
15.0.1 05 Mar 2025 U1 BSD-3-Clause Yes Details →
15.0.0 16 Feb 2025 U1 BSD-3-Clause Yes Details →
14.2.0 19 Jan 2025 U1 BSD-3-Clause Yes Details →
14.1.0 13 Nov 2024 U1 BSD-3-Clause Yes Details →
14.0.0 09 Nov 2024 U1 BSD-3-Clause Yes Details →
13.1.0 21 Sep 2024 U1 BSD-3-Clause Yes Details →
13.0.1 28 Aug 2024 U1 BSD-3-Clause Yes Details →
13.0.0 20 Aug 2024 U1 BSD-3-Clause Yes Details →
12.0.0 21 Oct 2023 U1 BSD-3-Clause Yes Details →
11.0.3 07 May 2023 U1 BSD-3-Clause Yes Details →
11.0.2 18 Apr 2023 U1 BSD-3-Clause Yes Details →
11.0.1 06 Apr 2023 U1 BSD-3-Clause Yes Details →
11.0.0 02 Apr 2023 U1 BSD-3-Clause Yes Details →
10.4.0 25 Oct 2022 U1 non-standard Yes Details →
10.3.0 17 Apr 2022 U1 non-standard Yes Details →
10.2.0 21 Feb 2022 U1 non-standard Yes Details →
10.1.0 14 Nov 2021 U1 non-standard Yes Details →
10.0.0 09 Sep 2021 U1 non-standard Yes Details →
9.1.0 27 May 2021 U1 non-standard Yes Details →
9.0.2 15 May 2021 H1 U1 non-standard Yes Details →
9.0.1 02 May 2021 H1 U1 non-standard Yes Details →
9.0.0 01 May 2021 H1 U1 non-standard Yes Details →
8.1.0 12 Nov 2019 H1 U1 non-standard Yes Details →
8.0.2 31 Jul 2019 H1 U1 non-standard Yes Details →
8.0.1 21 Jul 2019 H1 U1 non-standard Yes Details →
8.0.0 07 Jul 2019 H1 U1 non-standard Yes Details →
7.0.0 01 Nov 2018 H1 U1 non-standard Yes Details →
6.0.0 16 Jul 2018 H1 U1 non-standard Yes Details →
5.0.1 24 May 2018 H1 U1 non-standard Yes Details →
5.0.0 22 May 2018 H1 U1 non-standard Yes Details →
4.0.1 02 Nov 2017 H2 U2 non-standard Yes Details →
3.4.0 20 Aug 2017 H1 U2 non-standard Yes Details →
3.3.0 29 Mar 2017 H1 U2 non-standard Yes Details →
3.2.0 17 Aug 2016 H1 U2 non-standard Yes Details →
3.1.0 21 Apr 2016 H1 U2 non-standard Yes Details →
3.0.0 25 Dec 2015 H1 U2 non-standard Yes Details →
2.7.0 18 Nov 2015 H1 U2 non-standard Yes Details →
2.6.0 18 Aug 2015 H1 U2 non-standard Yes Details →
2.5.0 28 Jul 2015 H1 U2 non-standard Yes Details →
2.4.0 31 Jan 2015 H1 U2 non-standard Yes Details →
2.3.0 03 Nov 2014 H1 U2 non-standard Yes Details →
2.2.0 28 Jul 2014 H1 U2 non-standard Yes Details →
2.1.0 26 Apr 2014 H1 U2 non-standard Yes Details →
2.0.0 17 Mar 2014 H1 U2 non-standard Yes Details →
1.0.0 14 Nov 2013 H1 U2 non-standard Yes Details →
4.0.0 — H2 U2 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 2
  • 2021 2

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

03 Vulnerabilities

Recorded vulnerabilities for websockets

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-1000518: Denial of Service vulnerability in Python websockets library 7.5 high 5.0 17 Sep 2018
CVE-2021-33880: Observable Timing Discrepancy in aaugustin websockets library 5.9 high 9.1 11 Jun 2021
CVE-2018-1000518: websockets Denial of Service Vulnerability N/A unrated 5.0 26 Jun 2018
CVE-2021-33880: Timing Attack Vulnerability in websockets N/A unrated 547a26b685d08cac0aa64e5e65f7867ac0ea9bc0 06 Jun 2021

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 websockets

Is websockets safe to use?

Vulert records 4 vulnerabilities for websockets in PyPI: 0 critical, 2 high, 0 medium and 0 low, plus 2 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is websockets's Vulert package health score?

Vulert scores websockets 86/100, which reads as healthy. 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).

Is the latest version of websockets affected?

Yes. 17.3.0, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

How many vulnerabilities does websockets have?

4 vulnerabilities are recorded for websockets in the PyPI ecosystem: 0 critical, 2 high, 0 medium and 0 low, plus 2 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 websockets vulnerabilities disclosed?

0 vulnerabilities were recorded for websockets in the last 12 months, and the oldest entry in this database dates to 26 Jun 2018. 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 websockets 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 websockets for upcoming vulnerabilities?

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