VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.postgresql:postgresql: vulnerability history, versions and safety

org.postgresql:postgresql is a package in the Maven ecosystem. Vulert records 15 vulnerabilities for it across 117 releases, from Feb 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
15 vulnerabilities recorded C2 H9 M3 L1
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 21 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all org.postgresql:postgresql vulnerabilities

Vulert verdict on org.postgresql:postgresql 42.7.14 i

Updated on 22 Oct 2026

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

Package health score 77/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 42.7.14 — unaffected i
  • Vulnerabilities on record 15 over 4 years · 2 in the last year i
  • Latest disclosure 21 Jul 2026 i
  • Highest CVSS 10.0 i
  • With no published fix 0 i
  • Depended on by 436 packages i
  • Stars 1,744 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence BSD-2-Clause i

Version list, release dates, licence and dependants published by Maven Central, 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 org.postgresql:postgresql, 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
42.2.29.jre7 07 Oct 2026 H1 M1 L1 BSD-2-Clause Yes Details →
42.7.14 07 Oct 2026 none BSD-2-Clause — Details →
42.7.13 06 Jul 2026 none BSD-2-Clause — Details →
42.7.12 29 Jun 2026 none BSD-2-Clause — Details →
42.7.11 28 Apr 2026 H1 BSD-2-Clause Yes Details →
42.7.10 11 Feb 2026 H2 BSD-2-Clause Yes Details →
42.7.9 15 Jan 2026 H2 BSD-2-Clause Yes Details →
42.7.8 18 Sep 2025 H2 BSD-2-Clause Yes Details →
42.7.7 11 Jun 2025 H2 BSD-2-Clause Yes Details →
42.7.6 28 May 2025 H3 BSD-2-Clause Yes Details →
42.7.5 14 Jan 2025 H3 BSD-2-Clause Yes Details →
42.7.4 22 Aug 2024 H3 BSD-2-Clause Yes Details →
42.7.3 14 Mar 2024 H1 BSD-2-Clause Yes Details →
42.6.2 13 Mar 2024 H1 BSD-2-Clause Yes Details →
42.5.6 13 Mar 2024 H1 BSD-2-Clause Yes Details →
42.4.5 13 Mar 2024 H1 BSD-2-Clause Yes Details →
42.3.10 13 Mar 2024 H1 BSD-2-Clause Yes Details →
42.2.29 13 Mar 2024 H1 M1 L1 BSD-2-Clause Yes Details →
42.2.28.jre7 21 Feb 2024 H1 M1 L1 BSD-2-Clause Yes Details →
42.2.28 21 Feb 2024 H1 M1 L1 BSD-2-Clause Yes Details →
42.3.9 21 Feb 2024 H1 BSD-2-Clause Yes Details →
42.4.4 21 Feb 2024 H1 BSD-2-Clause Yes Details →
42.5.5 21 Feb 2024 H1 BSD-2-Clause Yes Details →
42.6.1 21 Feb 2024 H1 BSD-2-Clause Yes Details →
42.7.2 20 Feb 2024 H1 BSD-2-Clause Yes Details →
42.7.1 06 Dec 2023 C1 H1 BSD-2-Clause Yes Details →
42.7.0 20 Nov 2023 C1 H1 BSD-2-Clause Yes Details →
42.6.0 17 Mar 2023 H1 BSD-2-Clause Yes Details →
42.5.4 16 Feb 2023 H1 BSD-2-Clause Yes Details →
42.5.3 03 Feb 2023 H1 BSD-2-Clause Yes Details →
42.5.2 31 Jan 2023 H1 BSD-2-Clause Yes Details →
42.5.1 23 Nov 2022 H1 BSD-2-Clause Yes Details →
42.4.3 23 Nov 2022 H1 BSD-2-Clause Yes Details →
42.3.8 23 Nov 2022 H1 BSD-2-Clause Yes Details →
42.2.27.jre6 23 Nov 2022 C1 H1 M1 L1 BSD-2-Clause Yes Details →
42.2.27.jre7 23 Nov 2022 C1 H1 M1 L1 BSD-2-Clause Yes Details →
42.2.27 23 Nov 2022 C1 H1 M1 L1 BSD-2-Clause Yes Details →
42.3.7 06 Sep 2022 H1 BSD-2-Clause Yes Details →
42.5.0 24 Aug 2022 H1 BSD-2-Clause Yes Details →
42.4.2 17 Aug 2022 H1 BSD-2-Clause Yes Details →
42.2.26.jre6 03 Aug 2022 C1 H1 M2 L1 BSD-2-Clause Yes Details →
42.2.26.jre7 03 Aug 2022 C1 H1 M2 L1 BSD-2-Clause Yes Details →
42.2.26 03 Aug 2022 C1 H1 M2 L1 BSD-2-Clause Yes Details →
42.4.1 03 Aug 2022 H1 BSD-2-Clause Yes Details →
42.4.0 09 Jun 2022 H1 BSD-2-Clause Yes Details →
42.3.6 24 May 2022 H1 BSD-2-Clause Yes Details →
42.3.5 04 May 2022 H1 BSD-2-Clause Yes Details →
42.3.4 15 Apr 2022 H1 BSD-2-Clause Yes Details →
42.3.3 15 Feb 2022 H1 BSD-2-Clause Yes Details →
42.2.25.jre7 01 Feb 2022 C1 H2 M2 L1 BSD-2-Clause Yes Details →
42.2.25.jre6 01 Feb 2022 C1 H2 M2 L1 BSD-2-Clause Yes Details →
42.2.25 01 Feb 2022 C1 H2 M2 L1 BSD-2-Clause Yes Details →
42.3.2 01 Feb 2022 H1 M1 L1 BSD-2-Clause Yes Details →
42.3.1 29 Oct 2021 H1 M1 L1 BSD-2-Clause Yes Details →
42.3.0 15 Oct 2021 H1 M1 L1 BSD-2-Clause Yes Details →
42.2.24.jre6 23 Sep 2021 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.24.jre7 23 Sep 2021 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.24 23 Sep 2021 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.23.jre6 06 Jul 2021 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.23.jre7 06 Jul 2021 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.23 06 Jul 2021 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.22.jre7 16 Jun 2021 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.22 16 Jun 2021 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.22.jre6 16 Jun 2021 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.21.jre6 10 Jun 2021 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.21 10 Jun 2021 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.21.jre7 10 Jun 2021 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.20 22 Apr 2021 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.20.jre6 22 Apr 2021 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.20.jre7 22 Apr 2021 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.19.jre7 18 Feb 2021 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.19 18 Feb 2021 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.19.jre6 18 Feb 2021 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.18.jre7 15 Oct 2020 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.18 15 Oct 2020 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.18.jre6 15 Oct 2020 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.17 09 Oct 2020 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.17.jre6 09 Oct 2020 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.17.jre7 09 Oct 2020 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.16.jre7 21 Aug 2020 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.16 21 Aug 2020 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.16.jre6 21 Aug 2020 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.15.jre7 07 Aug 2020 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.15 07 Aug 2020 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.15.jre6 07 Aug 2020 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.14 10 Jun 2020 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.14.jre6 10 Jun 2020 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.14.jre7 10 Jun 2020 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.13 04 Jun 2020 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.13.jre6 04 Jun 2020 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.13.jre7 04 Jun 2020 C1 H3 M2 L1 BSD-2-Clause Yes Details →
42.2.12.jre6 31 Mar 2020 C1 H4 M2 L1 non-standard Yes Details →
42.2.12.jre7 31 Mar 2020 C1 H4 M2 L1 non-standard Yes Details →
42.2.12 31 Mar 2020 C1 H4 M2 L1 BSD-2-Clause Yes Details →
42.2.11.jre6 10 Mar 2020 C1 H4 M2 L1 non-standard Yes Details →
42.2.11.jre7 10 Mar 2020 C1 H4 M2 L1 non-standard Yes Details →
42.2.11 10 Mar 2020 C1 H4 M2 L1 BSD-2-Clause Yes Details →
42.2.10.jre7 06 Feb 2020 C1 H4 M2 L1 non-standard Yes Details →
42.2.10.jre6 06 Feb 2020 C1 H4 M2 L1 non-standard Yes Details →
42.2.10 06 Feb 2020 C1 H4 M2 L1 BSD-2-Clause Yes Details →
42.2.9.jre6 07 Dec 2019 C1 H4 M2 L1 — Yes Details →
42.2.9.jre7 07 Dec 2019 C1 H4 M2 L1 — Yes Details →
42.2.9 07 Dec 2019 C1 H4 M2 L1 — Yes Details →
42.2.8.jre6 13 Sep 2019 C1 H4 M2 L1 — Yes Details →
42.2.8.jre7 13 Sep 2019 C1 H4 M2 L1 — Yes Details →
42.2.8 13 Sep 2019 C1 H4 M2 L1 — Yes Details →
42.2.7.jre7 10 Sep 2019 C1 H4 M2 L1 — Yes Details →
42.2.7.jre6 10 Sep 2019 C1 H4 M2 L1 — Yes Details →
42.2.7 10 Sep 2019 C1 H4 M2 L1 — Yes Details →
42.2.6.jre6 19 Jun 2019 C1 H4 M2 L1 — Yes Details →
42.2.6.jre7 19 Jun 2019 C1 H4 M2 L1 — Yes Details →
42.2.6 19 Jun 2019 C1 H4 M2 L1 — Yes Details →
42.2.5.jre6 27 Aug 2018 C1 H4 M2 L1 — Yes Details →
42.2.5.jre7 27 Aug 2018 C1 H4 M2 L1 — Yes Details →
42.2.5 27 Aug 2018 C1 H4 M2 L1 — Yes Details →
42.2.4.jre6 14 Jul 2018 C1 H4 M2 L1 — Yes Details →
42.2.4.jre7 14 Jul 2018 C1 H4 M2 L1 — Yes Details →
42.2.4 14 Jul 2018 C1 H4 M2 L1 — Yes Details →
42.2.3.jre6 12 Jul 2018 C1 H4 M2 L1 — Yes Details →
42.2.3.jre7 12 Jul 2018 C1 H4 M2 L1 — Yes Details →

The newest 120 of 204 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 10
  • 2024 2
  • 2025 1
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for org.postgresql:postgresql

The 5 most severe of 15 vulnerabilities recorded for this package

Search all 15 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2024-1597: SQL Injection in pgjdbc 10.0 critical 42.7.2 19 Feb 2024
CVE-2024-1597: SQL Injection in org.postgresql:postgresql 10.0 critical 42.2.28 21 Feb 2024
CVE-2020-25695: SQL Injection in org.postgresql:postgresql 8.8 high 13.1 15 Feb 2022
CVE-2026-54291: PostgreSQL JDBC Driver Silent Downgrade Vulnerability 8.2 high 42.7.12 21 Jul 2026
CVE-2025-49146: PostgreSQL JDBC Driver Allows Insecure Authentication Despite Channel Binding Requirement 8.2 high 42.7.7 11 Jun 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 org.postgresql:postgresql

Is org.postgresql:postgresql safe to use?

Vulert records 15 vulnerabilities for org.postgresql:postgresql in Maven: 2 critical, 9 high, 3 medium and 1 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 org.postgresql:postgresql's Vulert package health score?

Vulert scores org.postgresql:postgresql 77/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 org.postgresql:postgresql affected?

No. 42.7.14, 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 org.postgresql:postgresql should I use?

42.7.14 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 org.postgresql:postgresql have?

15 vulnerabilities are recorded for org.postgresql:postgresql in the Maven ecosystem: 2 critical, 9 high, 3 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.postgresql:postgresql vulnerabilities disclosed?

2 vulnerabilities were recorded for org.postgresql:postgresql in the last 12 months, and the oldest entry in this database dates to 02 Feb 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 org.postgresql:postgresql 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 org.postgresql:postgresql for upcoming vulnerabilities?

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