VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

pg8000: vulnerability history, versions and safety

pg8000 is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 96 releases, from Oct 2025 to Jul 2026. 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
2 in the last 12 months

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all pg8000 vulnerabilities

Vulert verdict on pg8000 1.31.5 i

Updated on 23 Oct 2026

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

Package health score 75/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Quiet

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

  • Current release 1.31.5 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 8.1 i
  • With no published fix 0 i
  • Depended on by 253 packages i
  • Stars 549 i
  • Last release 13 months ago i
  • Licence BSD-3-Clause 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 pg8000, 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
1.31.5 14 Sep 2025 none BSD-3-Clause — Details →
1.31.4 20 Jul 2025 H1 U1 BSD-3-Clause Yes Details →
1.31.3 19 Jul 2025 H1 U1 BSD-3-Clause Yes Details →
1.31.2 28 Apr 2024 H1 U1 BSD-3-Clause Yes Details →
1.31.1 01 Apr 2024 H1 U1 BSD-3-Clause Yes Details →
1.31.0 31 Mar 2024 H1 U1 BSD-3-Clause Yes Details →
1.30.5 22 Feb 2024 H1 U1 BSD-3-Clause Yes Details →
1.30.4 03 Jan 2024 H1 U1 BSD-3-Clause Yes Details →
1.30.3 31 Oct 2023 H1 U1 BSD-3-Clause Yes Details →
1.30.2 17 Sep 2023 H1 U1 BSD-3-Clause Yes Details →
1.30.1 29 Jul 2023 H1 U1 BSD-3-Clause Yes Details →
1.3.0 27 Jul 2023 H1 U1 BSD-3-Clause Yes Details →
1.29.8 16 Jun 2023 H1 U1 BSD-3-Clause Yes Details →
1.29.7 16 Jun 2023 H1 U1 BSD-3-Clause Yes Details →
1.29.6 29 May 2023 H1 U1 BSD-3-Clause Yes Details →
1.29.5 09 May 2023 H1 U1 BSD-3-Clause Yes Details →
1.29.4 14 Dec 2022 H1 U1 BSD-3-Clause Yes Details →
1.29.3 26 Oct 2022 H1 U1 BSD-3-Clause Yes Details →
1.29.2 09 Oct 2022 H1 U1 non-standard Yes Details →
1.29.1 23 May 2022 H1 U1 non-standard Yes Details →
1.29.0 21 May 2022 H1 U1 non-standard Yes Details →
1.28.3 18 May 2022 H1 U1 non-standard Yes Details →
1.28.2 17 May 2022 H1 U1 non-standard Yes Details →
1.28.1 17 May 2022 H1 U1 non-standard Yes Details →
1.28.0 17 May 2022 H1 U1 non-standard Yes Details →
1.27.1 16 May 2022 H1 U1 non-standard Yes Details →
1.27.0 16 May 2022 H1 U1 non-standard Yes Details →
1.26.1 23 Apr 2022 H1 U1 non-standard Yes Details →
1.26.0 18 Apr 2022 H1 U1 non-standard Yes Details →
1.25.0 17 Apr 2022 H1 U1 non-standard Yes Details →
1.24.2 15 Apr 2022 H1 U1 non-standard Yes Details →
1.24.1 02 Mar 2022 H1 U1 non-standard Yes Details →
1.24.0 06 Feb 2022 H1 U1 non-standard Yes Details →
1.23.0 13 Nov 2021 H1 U1 non-standard Yes Details →
1.22.1 10 Nov 2021 H1 U1 non-standard Yes Details →
1.22.0 13 Oct 2021 H1 U1 non-standard Yes Details →
1.21.3 10 Oct 2021 H1 U1 non-standard Yes Details →
1.21.2 14 Sep 2021 H1 U1 non-standard Yes Details →
1.21.1 25 Aug 2021 H1 U1 non-standard Yes Details →
1.21.0 31 Jul 2021 H1 U1 non-standard Yes Details →
1.20.0 03 Jul 2021 H1 U1 non-standard Yes Details →
1.19.5 18 May 2021 H1 U1 non-standard Yes Details →
1.19.4 03 May 2021 H1 U1 non-standard Yes Details →
1.19.3 24 Apr 2021 H1 U1 non-standard Yes Details →
1.19.2 07 Apr 2021 H1 U1 non-standard Yes Details →
1.19.1 03 Apr 2021 H1 U1 non-standard Yes Details →
1.19.0 28 Mar 2021 H1 U1 non-standard Yes Details →
1.18.0 06 Mar 2021 H1 U1 non-standard Yes Details →
1.17.0 30 Jan 2021 H1 U1 non-standard Yes Details →
1.16.6 10 Oct 2020 H1 U1 non-standard Yes Details →
1.16.5 07 Aug 2020 H1 U1 non-standard Yes Details →
1.16.4 03 Aug 2020 H1 U1 non-standard Yes Details →
1.16.3 26 Jul 2020 H1 U1 non-standard Yes Details →
1.16.2 25 Jul 2020 H1 U1 non-standard Yes Details →
1.16.1 18 Jul 2020 H1 U1 non-standard Yes Details →
1.16.0 11 Jul 2020 H1 U1 non-standard Yes Details →
1.15.3 14 Jun 2020 H1 U1 non-standard Yes Details →
1.15.2 16 Apr 2020 H1 U1 non-standard Yes Details →
1.15.1 04 Apr 2020 H1 U1 non-standard Yes Details →
1.15.0 04 Apr 2020 H1 U1 non-standard Yes Details →
1.14.1 23 Mar 2020 H1 U1 non-standard Yes Details →
1.14.0 21 Mar 2020 H1 U1 non-standard Yes Details →
1.13.2 30 Jun 2019 H1 U1 non-standard Yes Details →
1.13.1 06 Feb 2019 H1 U1 non-standard Yes Details →
1.12.5 06 Feb 2019 H1 U1 non-standard Yes Details →
1.12.4 05 Jan 2019 H1 U1 non-standard Yes Details →
1.12.3 22 Aug 2018 H1 U1 non-standard Yes Details →
1.12.2 28 Jun 2018 H1 U1 non-standard Yes Details →
1.12.1 13 Jun 2018 H1 U1 non-standard Yes Details →
1.12.0 12 Jun 2018 H1 U1 non-standard Yes Details →
1.11.0 16 Aug 2017 H1 U1 non-standard Yes Details →
1.10.6 10 Jun 2016 H1 U1 non-standard Yes Details →
1.10.5 04 Mar 2016 H1 U1 non-standard Yes Details →
1.10.4 27 Feb 2016 H1 U1 non-standard Yes Details →
1.10.3 07 Jan 2016 H1 U1 non-standard Yes Details →
1.10.2 17 Mar 2015 H1 U1 non-standard Yes Details →
1.10.1 15 Sep 2014 H1 U1 non-standard Yes Details →
1.10.0 30 Aug 2014 H1 U1 non-standard Yes Details →
1.9.14 02 Aug 2014 H1 U1 non-standard Yes Details →
1.9.13 27 Jul 2014 H1 U1 non-standard Yes Details →
1.9.12 22 Jul 2014 H1 U1 non-standard Yes Details →
1.9.11 20 Jul 2014 H1 U1 non-standard Yes Details →
1.9.10 08 Jun 2014 H1 U1 non-standard Yes Details →
1.9.9 12 May 2014 H1 U1 non-standard Yes Details →
1.9.8 05 May 2014 H1 U1 non-standard Yes Details →
1.9.7 26 Mar 2014 H1 U1 non-standard Yes Details →
1.9.6 26 Feb 2014 H1 U1 non-standard Yes Details →
1.9.5 15 Feb 2014 H1 U1 non-standard Yes Details →
1.9.4 18 Jan 2014 H1 U1 non-standard Yes Details →
1.9.3 16 Jan 2014 H1 U1 non-standard Yes Details →
1.9.2 17 Dec 2013 H1 U1 non-standard Yes Details →
1.9.1 15 Dec 2013 H1 U1 non-standard Yes Details →
1.9.0 01 Dec 2013 H1 U1 non-standard Yes Details →
1.5.0 04 Sep 2008 H1 U1 non-standard Yes Details →
1.05-py2.4 — H1 U1 — Yes Details →
1.05-py2.5 — H1 U1 — Yes Details →
1.05.win32 — H1 U1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for pg8000

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-61385: pg8000 SQL Injection Vulnerability via Crafted Python List Input 8.1 high 1.31.5 27 Oct 2025
CVE-2025-61385: pg8000 SQL Injection Vulnerability via Crafted Python List Input 8.1 high 1.31.5 07 Jul 2026

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 pg8000

Is pg8000 safe to use?

Vulert records 2 vulnerabilities for pg8000 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 pg8000's Vulert package health score?

Vulert scores pg8000 75/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 pg8000 affected?

No. 1.31.5, 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 pg8000 should I use?

1.31.5 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 pg8000 have?

2 vulnerabilities are recorded for pg8000 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 pg8000 vulnerabilities disclosed?

2 vulnerabilities were recorded for pg8000 in the last 12 months, and the oldest entry in this database dates to 27 Oct 2025. 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 pg8000 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 pg8000 for upcoming vulnerabilities?

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