VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

pgadmin4: vulnerability history, versions and safety

pgadmin4 is a package in the PyPI ecosystem. Vulert records 56 vulnerabilities for it across 76 releases, from Mar 2022 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
56 vulnerabilities recorded C6 H14 M8 U28
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
42 in the last 12 months

Most recent disclosure 13 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all pgadmin4 vulnerabilities

Vulert verdict on pgadmin4 9.18.0 i

Updated on 23 Oct 2026

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

Package health score 46/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

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

  • Current release 9.18.0 — unaffected i
  • Vulnerabilities on record 56 over 4 years · 42 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 9.9 i
  • With no published fix 0 i
  • Depended on by 1 packages i
  • Last release 1 month ago i
  • Licence non-standard 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 pgadmin4, 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
9.18.0 17 Sep 2026 none non-standard — Details →
9.17.0 31 Jul 2026 none non-standard — Details →
9.16.0 18 Jun 2026 none non-standard — Details →
9.15.0 11 May 2026 none non-standard — Details →
9.14.0 02 Apr 2026 C1 H5 M2 U8 non-standard Yes Details →
9.13.0 05 Mar 2026 C1 H5 M2 U8 non-standard Yes Details →
9.12.0 05 Feb 2026 C1 H5 M2 U8 non-standard Yes Details →
9.11.0 11 Dec 2025 C1 H6 M2 U9 non-standard Yes Details →
9.10.0 13 Nov 2025 C2 H6 M2 U10 non-standard Yes Details →
9.9.0 16 Oct 2025 C3 H8 M3 U14 non-standard Yes Details →
9.8.0 04 Sep 2025 C3 H8 M3 U14 non-standard Yes Details →
9.7.0 21 Aug 2025 C3 H9 M3 U15 non-standard Yes Details →
9.6.0 28 Jul 2025 C3 H9 M3 U15 non-standard Yes Details →
9.5.0 04 Jul 2025 C3 H9 M3 U15 non-standard Yes Details →
9.4.0 29 May 2025 C3 H9 M3 U15 non-standard Yes Details →
9.3.0 30 Apr 2025 C3 H9 M3 U15 non-standard Yes Details →
9.2.0 03 Apr 2025 C3 H9 M3 U15 non-standard Yes Details →
9.1.0 28 Feb 2025 C5 H9 M3 U17 non-standard Yes Details →
9.0.0 06 Feb 2025 C5 H9 M3 U17 non-standard Yes Details →
8.14.0 12 Dec 2024 C5 H9 M3 U17 non-standard Yes Details →
8.13.0 14 Nov 2024 C5 H9 M3 U17 non-standard Yes Details →
8.12.0 23 Sep 2024 C5 H9 M3 U17 non-standard Yes Details →
8.11.0 22 Aug 2024 C5 H10 M3 U18 non-standard Yes Details →
8.10.0 29 Jul 2024 C5 H10 M3 U18 non-standard Yes Details →
8.9.0 27 Jun 2024 C5 H10 M3 U18 non-standard Yes Details →
8.8.0 06 Jun 2024 C5 H10 M3 U18 non-standard Yes Details →
8.7.0 30 May 2024 C5 H10 M3 U18 non-standard Yes Details →
8.6.0 02 May 2024 C5 H10 M3 U18 non-standard Yes Details →
8.5.0 04 Apr 2024 C5 H11 M4 U20 non-standard Yes Details →
8.4.0 07 Mar 2024 C5 H12 M4 U21 non-standard Yes Details →
8.3.0 09 Feb 2024 C6 H12 M4 U22 non-standard Yes Details →
8.2.0 11 Jan 2024 C6 H12 M4 U22 non-standard Yes Details →
8.1.0 14 Dec 2023 C6 H12 M4 U22 non-standard Yes Details →
8.0.0 23 Nov 2023 C6 H12 M4 U22 non-standard Yes Details →
7.8.0 19 Oct 2023 C6 H12 M4 U22 non-standard Yes Details →
7.7.0 21 Sep 2023 C6 H12 M4 U22 non-standard Yes Details →
7.6.0 24 Aug 2023 C6 H12 M5 U23 non-standard Yes Details →
7.5.0 27 Jul 2023 C6 H12 M5 U23 non-standard Yes Details →
7.4.0 29 Jun 2023 C6 H12 M5 U23 non-standard Yes Details →
7.3.0 06 Jun 2023 C6 H12 M5 U23 non-standard Yes Details →
7.2.0 01 Jun 2023 C6 H12 M5 U23 non-standard Yes Details →
7.1.0 04 May 2023 C6 H12 M5 U23 non-standard Yes Details →
7.0.0 13 Apr 2023 C6 H12 M5 U23 non-standard Yes Details →
6.21.0 09 Mar 2023 C6 H13 M5 U24 non-standard Yes Details →
6.20.0 09 Feb 2023 C6 H13 M5 U24 non-standard Yes Details →
6.19.0 17 Jan 2023 C6 H13 M5 U24 non-standard Yes Details →
6.18.0 20 Dec 2022 C6 H13 M6 U25 non-standard Yes Details →
6.17.0 02 Dec 2022 C6 H13 M6 U25 non-standard Yes Details →
6.16.0 18 Nov 2022 C6 H14 M6 U26 non-standard Yes Details →
6.15.0 20 Oct 2022 C6 H14 M6 U26 non-standard Yes Details →
6.14.0 22 Sep 2022 C6 H14 M6 U26 non-standard Yes Details →
6.13.0 25 Aug 2022 C6 H14 M7 U27 non-standard Yes Details →
6.12.0 28 Jul 2022 C6 H14 M7 U27 non-standard Yes Details →
6.11.0 30 Jun 2022 C6 H14 M7 U27 non-standard Yes Details →
6.10.0 02 Jun 2022 C6 H14 M7 U27 non-standard Yes Details →
6.9.0 12 May 2022 C6 H14 M7 U27 non-standard Yes Details →
6.8.0 07 Apr 2022 C6 H14 M7 U27 non-standard Yes Details →
6.7.0 14 Mar 2022 C6 H14 M7 U27 non-standard Yes Details →
6.6.0 10 Mar 2022 C6 H14 M8 U28 non-standard Yes Details →
6.5.0 11 Feb 2022 C6 H14 M8 U28 non-standard Yes Details →
6.4.0 13 Jan 2022 C6 H14 M8 U28 non-standard Yes Details →
6.3.0 16 Dec 2021 C6 H14 M8 U28 non-standard Yes Details →
6.2.0 06 Dec 2021 C6 H14 M8 U28 non-standard Yes Details →
5.7.0 09 Sep 2021 C6 H14 M8 U28 non-standard Yes Details →
5.6.0 12 Aug 2021 C6 H14 M8 U28 non-standard Yes Details →
5.5.0 15 Jul 2021 C6 H14 M8 U28 non-standard Yes Details →
5.4.0 17 Jun 2021 C6 H14 M8 U28 non-standard Yes Details →
5.3.0 20 May 2021 C6 H14 M8 U28 non-standard Yes Details →
5.2.0 22 Apr 2021 C6 H14 M8 U28 non-standard Yes Details →
5.1.0 25 Mar 2021 C6 H14 M8 U28 non-standard Yes Details →
5.0.0 25 Feb 2021 C6 H14 M8 U28 non-standard Yes Details →
4.30.0 28 Jan 2021 C6 H14 M8 U28 non-standard Yes Details →
4.29.0 10 Dec 2020 C6 H14 M8 U28 non-standard Yes Details →
4.28.0 12 Nov 2020 C6 H14 M8 U28 non-standard Yes Details →
4.27.0 15 Oct 2020 C6 H14 M8 U28 non-standard Yes Details →
4.26.0 17 Sep 2020 C6 H14 M8 U28 non-standard Yes Details →
4.25.0 20 Aug 2020 C6 H14 M8 U28 non-standard Yes Details →
4.24.0 23 Jul 2020 C6 H14 M8 U28 non-standard Yes Details →
4.23.0 25 Jun 2020 C6 H14 M8 U28 non-standard Yes Details →
4.22.0 28 May 2020 C6 H14 M8 U28 non-standard Yes Details →

All 80 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 2
  • 2023 3
  • 2024 5
  • 2025 9
  • 2026 37

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

03 Vulnerabilities

Recorded vulnerabilities for pgadmin4

The 5 most severe of 56 vulnerabilities recorded for this package

Search all 56 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-7813: pgAdmin 4 Authorization Vulnerability in Server Mode 9.9 critical 9.15 11 May 2026
CVE-2026-7813: pgAdmin 4 Authorization Vulnerability in Server Mode 9.9 critical 9.15 29 Jun 2026
CVE-2025-2945: pgAdmin 4 Remote Code Execution Vulnerability 9.9 critical 9.2 29 Jun 2026
CVE-2024-2044: pgAdmin 4 Vulnerable to Unsafe Deserialization and Remote Code Execution 9.9 critical 8.4 29 Jun 2026
Unsafe Deserialization and Remote Code Execution in pgAdmin 4 9.9 critical 8.4 07 Mar 2024

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 pgadmin4

Is pgadmin4 safe to use?

Vulert records 56 vulnerabilities for pgadmin4 in PyPI: 6 critical, 14 high, 8 medium and 0 low, plus 28 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 pgadmin4's Vulert package health score?

Vulert scores pgadmin4 46/100, which reads as risky. 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 pgadmin4 affected?

No. 9.18.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 pgadmin4 should I use?

9.18.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 pgadmin4 have?

56 vulnerabilities are recorded for pgadmin4 in the PyPI ecosystem: 6 critical, 14 high, 8 medium and 0 low, plus 28 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 pgadmin4 vulnerabilities disclosed?

42 vulnerabilities were recorded for pgadmin4 in the last 12 months, and the oldest entry in this database dates to 17 Mar 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 pgadmin4 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 pgadmin4 for upcoming vulnerabilities?

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