org.postgresql:postgresql
Maven package
Overview
Package versions
| Versions | Range | Direct vulnerabilities |
|---|---|---|
| 42.7.12 | and later versions | 0C0H0M0L |
| 42.7.11 | up to 42.7.12 | 0C1H0M0L |
| 42.7.7 | up to 42.7.11 | 0C2H0M0L |
| 42.7.4 | up to 42.7.7 | 0C2H1M0L |
| 42.7.2 | up to 42.7.4 | 0C1H0M0L |
| 42.7.0 | up to 42.7.2 | 1C1H0M0L |
| 42.6.1 | up to 42.7.0 | 0C1H0M0L |
| 42.6.0 | up to 42.6.1 | 1C1H0M0L |
| 42.5.5 | up to 42.6.0 | 0C1H0M0L |
| 42.5.1 | up to 42.5.5 | 1C1H0M0L |
| 42.5.0 | up to 42.5.1 | 1C1H1M0L |
| 42.4.4 | up to 42.5.0 | 0C1H0M0L |
| 42.4.3 | up to 42.4.4 | 1C1H0M0L |
| 42.4.1 | up to 42.4.3 | 1C1H1M0L |
| 42.4.0 | up to 42.4.1 | 1C2H1M0L |
| 42.3.9 | up to 42.4.0 | 0C1H0M0L |
| 42.3.8 | up to 42.3.9 | 1C1H0M0L |
| 42.3.7 | up to 42.3.8 | 1C1H1M0L |
| 42.3.3 | up to 42.3.7 | 1C2H1M0L |
| 42.3.2 | up to 42.3.3 | 2C2H2M0L |
| 42.3.0 | up to 42.3.2 | 3C2H2M0L |
| 42.2.28 | up to 42.3.0 | 1C1H1M0L |
| 42.2.27 | up to 42.2.28 | 2C1H1M0L |
| 42.2.26 | up to 42.2.27 | 2C1H2M0L |
| 42.2.25 | up to 42.2.26 | 2C2H2M0L |
| 42.2.13 | up to 42.2.25 | 3C2H2M0L |
| 42.2.0 | up to 42.2.13 | 3C3H2M0L |
| 42.1.0 | up to 42.2.0 | 3C2H1M0L |
| 9.4.1212.jre6 | up to 42.1.0 | 2C2H0M0L |
| 9.4.1208 | up to 9.4.1212.jre6 | 2C1H0M0L |
| 8.2 | up to 9.4.1208 | 1C1H0M0L |
| before 8.2 | all earlier versions | 1C2H0M0L |
No known vulnerabilities in 42.7.12 and later versions
Nothing in our data affects this version.
32 ranges in total. Each row is a range of versions with the same vulnerabilities, newest first. The data names only the versions where something changes (first affected, fixed), so the versions in between are a range.
Vulnerabilities · 11
| CVE | Severity | Published | Vulnerable | Fixed in |
|---|---|---|---|---|
| CVE-2026-54291org.postgresql/postgresql: com.ongres.scram/scram-client: pgjdbc: Man-in-the-middle protection bypass via SCRAM-SHA-256-PLUS downgrade | HIGH | 6 Jul 2026 | >=42.7.4, <42.7.12 | 42.7.12 |
| CVE-2026-42198jdbc.postgresql.org: pgjdbc: Client-side Denial of Service via malicious SCRAM-SHA-256 authentication | HIGH | 29 Apr 2026 | >=42.2.0, <42.7.11 | 42.7.11 |
| CVE-2025-49146pgjdbc: pgjdbc insecure authentication in channel binding | MEDIUM | 11 Jun 2025 | >=42.7.4, <42.7.7 | 42.7.7 |
| CVE-2024-1597pgjdbc: PostgreSQL JDBC Driver allows attacker to inject SQL if using PreferQueryMode=SIMPLE | CRITICAL | 19 Feb 2024 | <42.2.28>=42.3.0, <42.3.9>=42.4.0, <42.4.4>=42.5.0, <42.5.5>=42.6.0, <42.6.1>=42.7.0, <42.7.2 | 42.2.2842.3.942.4.442.5.542.6.142.7.2 |
| CVE-2022-41946postgresql-jdbc: Information leak of prepared statement data due to insecure temporary file permissions | MEDIUM | 23 Nov 2022 | >=42.2.0, <42.2.27>=42.3.0, <42.3.8>=42.4.0, <42.4.3>=42.5.0, <42.5.1 | 42.2.2742.3.842.4.342.5.1 |
| CVE-2022-31197postgresql: SQL Injection in ResultSet.refreshRow() with malicious column names | HIGH | 3 Aug 2022 | <42.2.26>=42.4.0, <42.4.1>=42.3.0, <42.3.7 | 42.2.2642.4.142.3.7 |
| CVE-2022-26520postgresql-jdbc: Arbitrary File Write Vulnerability | CRITICAL | 10 Mar 2022 | >=42.1.0, <42.3.3 | 42.3.3 |
| GHSA-673J-QM5F-XPV8pgjdbc Arbitrary File Write Vulnerability | MEDIUM | 16 Feb 2022 | >=42.1.0, <42.3.3 | 42.3.3 |
| CVE-2022-21724jdbc-postgresql: Unchecked Class Instantiation when providing Plugin Classes | CRITICAL | 2 Feb 2022 | >=9.4.1208, <42.2.25>=42.3.0, <42.3.2 | 42.2.2542.3.2 |
| CVE-2020-13692postgresql-jdbc: XML external entity (XXE) vulnerability in PgSQLXML | HIGH | 4 Jun 2020 | >=9.4.1212.jre6, <42.2.13 | 42.2.13 |
| CVE-2012-1618postgresql-jdbc: SQL injection due improper escaping of JDBC statement parameters | HIGH | 6 Oct 2012 | <8.2 | 8.2 |
Seal Security (Maven)
Seal Security ships a patched build of this package. Its fixed versions:
- CVE-2026-107313: 42.7.4+sp999, 42.7.5+sp999
- CVE-2026-107315: 42.7.4+sp999, 42.7.5+sp999
- CVE-2026-42198: 42.7.4+sp999, 42.7.5+sp2
- CVE-2026-54291: 42.7.4+sp999, 42.7.5+sp2
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.