Is org.postgresql:postgresql 42.3 vulnerable?
Maven · 11 releases from 42.3.0 to 42.3.10 · latest org.postgresql:postgresql is 42.7.14 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. org.postgresql:postgresql 42.3.10, the last 42.3 release, is affected by 1 known security advisory (1 high), including CVE-2026-42198. 6 more affect earlier 42.3.x releases. Upgrade to 42.7.11 or later to fix all of them.
mvn versions:use-dep-version -Dincludes=org.postgresql:postgresql -DdepVersion=42.7.11 -DforceVersion=trueIs your project on an affected org.postgresql:postgresql?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting org.postgresql:postgresql 42.3.10
pgjdbc: Unbounded PBKDF2 iterations in SCRAM authentication allows CPU exhaustion DoS
- Affected
- >=42.2.0 <42.7.11
- Fixed in
- 42.7.11
Fixed within 42.3.x, affecting earlier releases
org.postgresql:postgresql vulnerable to SQL Injection via line comment generation
- Affected
- <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
- Fixed in
- 42.2.28, 42.3.9, 42.4.4, 42.5.5, 42.6.1, 42.7.2
TemporaryFolder on unix-like systems does not limit access to created files
- Affected
- >=42.2.0 <42.2.27 · >=42.3.0 <42.3.8 · >=42.4.0 <42.4.3 · >=42.5.0 <42.5.1
- Fixed in
- 42.2.27, 42.3.8, 42.4.3, 42.5.1
PostgreSQL JDBC Driver SQL Injection in ResultSet.refreshRow() with malicious column names
- Affected
- <42.2.26 · >=42.4.0 <42.4.1 · >=42.3.0 <42.3.7
- Fixed in
- 42.2.26, 42.3.7, 42.4.1
Path traversal in org.postgresql:postgresql
- Affected
- >=42.1.0 <42.3.3
- Fixed in
- 42.3.3
pgjdbc Arbitrary File Write Vulnerability
- Affected
- >=42.1.0 <42.3.3
- Fixed in
- 42.3.3
pgjdbc Does Not Check Class Instantiation when providing Plugin Classes
- Affected
- >=9.4.1208 <42.2.25 · >=42.3.0 <42.3.2
- Fixed in
- 42.2.25, 42.3.2
Every org.postgresql:postgresql 42.3.x release
Affected: 42.3.0 to 42.3.10. Latest org.postgresql:postgresql: 42.7.14.
| Version | Known advisories |
|---|---|
| org.postgresql:postgresql 42.3.10 | CVE-2026-42198 |
| org.postgresql:postgresql 42.3.9 | CVE-2026-42198 |
| org.postgresql:postgresql 42.3.8 | CVE-2026-42198, CVE-2024-1597 |
| org.postgresql:postgresql 42.3.7 | CVE-2026-42198, CVE-2024-1597, CVE-2022-41946 |
| org.postgresql:postgresql 42.3.6 | CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197 |
| org.postgresql:postgresql 42.3.5 | CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197 |
| org.postgresql:postgresql 42.3.4 | CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197 |
| org.postgresql:postgresql 42.3.3 | CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197 |
| org.postgresql:postgresql 42.3.2 | CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197, CVE-2022-26520, CVE-2022-26520 |
| org.postgresql:postgresql 42.3.1 | CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197, CVE-2022-26520, CVE-2022-26520, CVE-2022-21724 |
| org.postgresql:postgresql 42.3.0 | CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197, CVE-2022-26520, CVE-2022-26520, CVE-2022-21724 |
Which of your client projects are still on org.postgresql:postgresql 42.3?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.postgresql:postgresql version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other org.postgresql:postgresql versions
- org.postgresql:postgresql 42.6
- org.postgresql:postgresql 42.5
- org.postgresql:postgresql 42.4
- org.postgresql:postgresql 42.2
- org.postgresql:postgresql 42.1
- org.postgresql:postgresql 42.0
- org.postgresql:postgresql 42.7
- org.postgresql:postgresql 9.4
- org.postgresql:postgresql 9.3
- org.postgresql:postgresql 9.2
- All org.postgresql:postgresql advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.