VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

pywps: vulnerability history, versions and safety

pywps is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 27 releases, from Aug 2021 to Sep 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 U1
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 pywps vulnerabilities

Vulert verdict on pywps 4.8.1 i

Updated on 23 Oct 2026

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

Package health score 81/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

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

  • Current release 4.8.1 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 02 Sep 2021 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 4 packages i
  • Stars 186 i
  • Last release this month i
  • Licence MIT 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 pywps, 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
4.8.1 06 Oct 2026 none MIT — Details →
4.8.0 14 Sep 2026 none MIT — Details →
4.7.0 15 Dec 2025 none MIT — Details →
4.6.0 03 Nov 2023 none MIT — Details →
4.5.2 13 Apr 2022 none MIT — Details →
4.5.1 01 Dec 2021 none MIT — Details →
4.5.0 12 Aug 2021 none MIT — Details →
4.4.5 11 Aug 2021 H1 U1 MIT Yes Details →
4.4.4 03 Jun 2021 H1 U1 MIT Yes Details →
4.4.3 10 May 2021 H1 U1 MIT Yes Details →
4.4.2 31 Mar 2021 H1 U1 MIT Yes Details →
4.4.1 21 Mar 2021 H1 U1 MIT Yes Details →
4.4.0 15 Feb 2021 H1 U1 MIT Yes Details →
4.2.11 05 Feb 2021 H1 U1 MIT Yes Details →
4.2.10 25 Jan 2021 H1 U1 MIT Yes Details →
4.2.9 11 Dec 2020 H1 U1 MIT Yes Details →
4.2.8 16 Sep 2020 H1 U1 MIT Yes Details →
4.2.7 05 Aug 2020 H1 U1 MIT Yes Details →
4.2.6 03 Jul 2020 H1 U1 MIT Yes Details →
4.2.5 03 Jul 2020 H1 U1 MIT Yes Details →
4.2.4 14 May 2020 H1 U1 MIT Yes Details →
4.2.3 10 Nov 2019 H1 U1 MIT Yes Details →
4.2.2 25 Sep 2019 H1 U1 MIT Yes Details →
4.2.1 17 Dec 2018 H1 U1 MIT Yes Details →
4.2.0 17 Dec 2018 H1 U1 MIT Yes Details →
4.0.0 04 Jun 2017 H1 U1 MIT Yes Details →
3.2.6 01 Jul 2016 H1 U1 non-standard Yes Details →
3.2.3-py2.7 — H1 U1 — Yes Details →
3.2.4-py2.7 — H1 U1 — Yes Details →
3.2.5-py2.7 — H1 U1 — Yes Details →
3.2.6-py2.7 — H1 U1 — Yes Details →
4.0.0-py2.7 — H1 U1 — Yes Details →
4.0.0-py3.5 — H1 U1 — Yes Details →
trunk-py2.7 — H1 U1 — Yes Details →

All 34 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 2

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

03 Vulnerabilities

Recorded vulnerabilities for pywps

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-39371: XML External Entity Injection in PyWPS 7.5 high 4.5.0 02 Sep 2021
CVE-2021-39371: XXE Injection in PyWPS N/A unrated 4.5.0 23 Aug 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 pywps

Is pywps safe to use?

Vulert records 2 vulnerabilities for pywps in PyPI: 0 critical, 1 high, 0 medium and 0 low, plus 1 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 pywps's Vulert package health score?

Vulert scores pywps 81/100, which reads as in good shape. 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 pywps affected?

No. 4.8.1, 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 pywps should I use?

4.8.1 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 pywps have?

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

0 vulnerabilities were recorded for pywps in the last 12 months, and the oldest entry in this database dates to 23 Aug 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 pywps 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 pywps for upcoming vulnerabilities?

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