VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

pycsw: vulnerability history, versions and safety

pycsw is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 21 releases, first recorded in Aug 2018. 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 C1 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 pycsw vulnerabilities

Vulert verdict on pycsw 2.6.2 i

Updated on 23 Oct 2026

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

Package health score 71/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Not enough data

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

  • Current release 2.6.2 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 15 Aug 2018 i
  • Highest CVSS 9.1 i
  • With no published fix 0 i
  • Depended on by 2 packages i
  • Last release 20 months ago i
  • Licence MIT 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 pycsw, 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.6.2 22 Feb 2025 none MIT — Details →
2.6.1 14 Oct 2021 none MIT — Details →
2.6.0 05 Dec 2020 none MIT — Details →
2.4.2 17 Jan 2020 none MIT — Details →
2.4.1 31 Aug 2019 none MIT — Details →
2.4.0 17 May 2019 none MIT — Details →
2.2.0 20 Mar 2018 none MIT — Details →
2.0.3 02 Jun 2017 none MIT — Details →
1.8.6 19 Oct 2016 none MIT — Details →
1.10.5 18 Oct 2016 none MIT — Details →
2.0.2 18 Oct 2016 none MIT — Details →
2.0.1 08 Sep 2016 C1 U1 MIT Yes Details →
2.0.0 11 Jul 2016 C1 U1 MIT Yes Details →
2.0.0a1 08 Jun 2016 none MIT — Details →
1.10.4 23 Apr 2016 U1 MIT Yes Details →
1.8.5 20 Oct 2015 U1 MIT Yes Details →
1.10.3 19 Oct 2015 U1 MIT Yes Details →
1.8.4 26 Jun 2015 U1 MIT Yes Details →
1.10.2 26 Jun 2015 U1 MIT Yes Details →
1.10.1 29 Dec 2014 U1 MIT Yes Details →
1.10.0 13 Sep 2014 U1 MIT Yes Details →
1.8.3 21 Jun 2014 U1 MIT Yes Details →
1.8.2 28 May 2014 U1 MIT Yes Details →
1.8.1 19 May 2014 U1 MIT Yes Details →
1.6.4 27 Mar 2014 U1 MIT Yes Details →
1.8.0 20 Mar 2014 U1 MIT Yes Details →
1.6.3 12 Mar 2014 U1 MIT Yes Details →
1.6.2 11 Mar 2014 U1 MIT Yes Details →
1.6.1 22 Aug 2013 U1 MIT Yes Details →
1.6.0 28 Jun 2013 U1 MIT Yes Details →
1.4.2 07 Jun 2013 U1 MIT Yes Details →
1.4.1 26 Mar 2013 U1 MIT Yes Details →
1.4.0 10 Sep 2012 U1 MIT Yes Details →

All 33 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

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 pycsw

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2016-8640: SQL Injection in pycsw 9.1 critical 2.0.2 15 Aug 2018
CVE-2016-8640: SQL Injection Vulnerability in pycsw N/A unrated 2.0.2 01 Aug 2018

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 pycsw

Is pycsw safe to use?

Vulert records 2 vulnerabilities for pycsw in PyPI: 1 critical, 0 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 pycsw's Vulert package health score?

Vulert scores pycsw 71/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 pycsw affected?

No. 2.6.2, 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 pycsw should I use?

2.6.2 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 pycsw have?

2 vulnerabilities are recorded for pycsw in the PyPI ecosystem: 1 critical, 0 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 pycsw vulnerabilities disclosed?

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

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