Is org.postgresql:postgresql 42.2 vulnerable?

Maven · 30 releases from 42.2.0 to 42.2.29 · latest org.postgresql:postgresql is 42.7.14 · checked 18 Nov 2026

Yes: 3 known advisories

Yes. org.postgresql:postgresql 42.2.29, the last 42.2 release, is affected by 3 known security advisories (1 high, 1 medium, 1 low), including CVE-2026-42198, CVE-2022-26520, CVE-2022-26520. 5 more affect earlier 42.2.x releases. Upgrade to 42.7.11 or later to fix all of them.

Upgrade with:mvn versions:use-dep-version -Dincludes=org.postgresql:postgresql -DdepVersion=42.7.11 -DforceVersion=true

Is your project on an affected org.postgresql:postgresql?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

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.2.29

  • HighCVE-2026-42198GHSA-98qh-xjc8-98pq5 May 2026

    pgjdbc: Unbounded PBKDF2 iterations in SCRAM authentication allows CPU exhaustion DoS

    Affected
    >=42.2.0 <42.7.11
    Fixed in
    42.7.11
  • LowCVE-2022-26520GHSA-727h-hrw8-jg8q11 Mar 2022

    Path traversal in org.postgresql:postgresql

    Affected
    >=42.1.0 <42.3.3
    Fixed in
    42.3.3
  • MediumCVE-2022-26520GHSA-673j-qm5f-xpv816 Feb 2022

    pgjdbc Arbitrary File Write Vulnerability

    Affected
    >=42.1.0 <42.3.3
    Fixed in
    42.3.3

Fixed within 42.2.x, affecting earlier releases

  • CriticalCVE-2024-1597GHSA-24rp-q3w6-vc5621 Feb 2024

    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
  • MediumCVE-2022-41946GHSA-562r-vg33-8x8h23 Nov 2022

    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
  • HighCVE-2022-31197GHSA-r38f-c4h4-hqq26 Aug 2022

    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
  • HighCVE-2020-13692GHSA-88cc-g835-76rp10 Feb 2022

    Improper Restriction of XML External Entity Reference

    Affected
    >=9.4.1212.jre6 <42.2.13
    Fixed in
    42.2.13
  • HighCVE-2022-21724GHSA-v7wg-cpwc-24m42 Feb 2022

    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.2.x release

Affected: 42.2.0 to 42.2.29. Latest org.postgresql:postgresql: 42.7.14.

VersionKnown advisories
org.postgresql:postgresql 42.2.29CVE-2026-42198, CVE-2022-26520, CVE-2022-26520
org.postgresql:postgresql 42.2.28CVE-2026-42198, CVE-2022-26520, CVE-2022-26520
org.postgresql:postgresql 42.2.27CVE-2026-42198, CVE-2024-1597, CVE-2022-26520, CVE-2022-26520
org.postgresql:postgresql 42.2.26CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-26520, CVE-2022-26520
org.postgresql:postgresql 42.2.25CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197, CVE-2022-26520, CVE-2022-26520
org.postgresql:postgresql 42.2.24CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197, CVE-2022-26520, CVE-2022-26520, CVE-2022-21724
org.postgresql:postgresql 42.2.23CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197, CVE-2022-26520, CVE-2022-26520, CVE-2022-21724
org.postgresql:postgresql 42.2.22CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197, CVE-2022-26520, CVE-2022-26520, CVE-2022-21724
org.postgresql:postgresql 42.2.21CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197, CVE-2022-26520, CVE-2022-26520, CVE-2022-21724
org.postgresql:postgresql 42.2.20CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197, CVE-2022-26520, CVE-2022-26520, CVE-2022-21724
org.postgresql:postgresql 42.2.19CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197, CVE-2022-26520, CVE-2022-26520, CVE-2022-21724
org.postgresql:postgresql 42.2.18CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197, CVE-2022-26520, CVE-2022-26520, CVE-2022-21724
org.postgresql:postgresql 42.2.17CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197, CVE-2022-26520, CVE-2022-26520, CVE-2022-21724
org.postgresql:postgresql 42.2.16CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197, CVE-2022-26520, CVE-2022-26520, CVE-2022-21724
org.postgresql:postgresql 42.2.15CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197, CVE-2022-26520, CVE-2022-26520, CVE-2022-21724
org.postgresql:postgresql 42.2.14CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197, CVE-2022-26520, CVE-2022-26520, CVE-2022-21724
org.postgresql:postgresql 42.2.13CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197, CVE-2022-26520, CVE-2022-26520, CVE-2022-21724
org.postgresql:postgresql 42.2.12CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197, CVE-2022-26520, CVE-2022-26520, CVE-2020-13692, CVE-2022-21724
org.postgresql:postgresql 42.2.11CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197, CVE-2022-26520, CVE-2022-26520, CVE-2020-13692, CVE-2022-21724
org.postgresql:postgresql 42.2.10CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197, CVE-2022-26520, CVE-2022-26520, CVE-2020-13692, CVE-2022-21724
org.postgresql:postgresql 42.2.9CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197, CVE-2022-26520, CVE-2022-26520, CVE-2020-13692, CVE-2022-21724
org.postgresql:postgresql 42.2.8CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197, CVE-2022-26520, CVE-2022-26520, CVE-2020-13692, CVE-2022-21724
org.postgresql:postgresql 42.2.7CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197, CVE-2022-26520, CVE-2022-26520, CVE-2020-13692, CVE-2022-21724
org.postgresql:postgresql 42.2.6CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197, CVE-2022-26520, CVE-2022-26520, CVE-2020-13692, CVE-2022-21724
org.postgresql:postgresql 42.2.5CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197, CVE-2022-26520, CVE-2022-26520, CVE-2020-13692, CVE-2022-21724
org.postgresql:postgresql 42.2.4CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197, CVE-2022-26520, CVE-2022-26520, CVE-2020-13692, CVE-2022-21724
org.postgresql:postgresql 42.2.3CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197, CVE-2022-26520, CVE-2022-26520, CVE-2020-13692, CVE-2022-21724
org.postgresql:postgresql 42.2.2CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197, CVE-2022-26520, CVE-2022-26520, CVE-2020-13692, CVE-2022-21724
org.postgresql:postgresql 42.2.1CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197, CVE-2022-26520, CVE-2022-26520, CVE-2020-13692, CVE-2022-21724
org.postgresql:postgresql 42.2.0CVE-2026-42198, CVE-2024-1597, CVE-2022-41946, CVE-2022-31197, CVE-2022-26520, CVE-2022-26520, CVE-2020-13692, CVE-2022-21724

Which of your client projects are still on org.postgresql:postgresql 42.2?

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

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.