VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

phoenix-ws: vulnerability history, versions and safety

phoenix-ws is a package in the PyPI ecosystem. Vulert records 1 vulnerability for it across 2 releases, first recorded in Jun 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
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 phoenix-ws vulnerabilities

Vulert verdict on phoenix-ws 2.1.0 i

Updated on 23 Oct 2026

Good news: 2.1.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 64/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Inactive

What to do: Stay on 2.1.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.1.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.1.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 02 Jun 2022 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 2 i
  • Last release 19 months ago i
  • Licence Unlicense i

Version list, release dates, licence and dependants published by PyPI, 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 phoenix-ws, 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
2.1.0 10 Mar 2025 none Unlicense — Details →
2.0.9 08 Mar 2025 none Unlicense — Details →
2.0.8 08 Mar 2025 none Unlicense — Details →
2.0.7 15 Feb 2024 none Unlicense — Details →
2.0.5 31 Jan 2024 none Unlicense — Details →
2.0.4 28 Jan 2024 none Unlicense — Details →
2.0.3 12 Jan 2024 none MIT — Details →
2.0.2 25 Aug 2023 none MIT — Details →
2.0.1 07 Mar 2023 none MIT — Details →
2.0.0.3 24 Nov 2022 none MIT — Details →
2.0.0.2 24 Nov 2022 none MIT — Details →
2.0.0.1 03 Nov 2022 none MIT — Details →
2.0.0.post1 03 Nov 2022 none MIT — Details →
1.0.7.1 27 May 2022 none MIT — Details →
1.0.7 27 May 2022 none MIT — Details →
1.0.6 26 May 2022 none MIT — Details →
1.0.4.1 26 May 2022 H1 MIT Yes Details →
1.0.4 26 May 2022 H1 MIT Yes Details →
2.0.0.1-py3.10 — none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for phoenix-ws

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Publicly Available Source Code in Phoenix-ws Extensions Folder 7.5 high 1.0.6 02 Jun 2022

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 phoenix-ws

Is phoenix-ws safe to use?

Vulert records 1 vulnerabilities for phoenix-ws in PyPI: 0 critical, 1 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is phoenix-ws's Vulert package health score?

Vulert scores phoenix-ws 64/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).

Is the latest version of phoenix-ws affected?

No. 2.1.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of phoenix-ws should I use?

2.1.0 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 phoenix-ws have?

1 vulnerability is recorded for phoenix-ws in the PyPI ecosystem: 0 critical, 1 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new phoenix-ws vulnerabilities disclosed?

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

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