Is org.postgresql:postgresql 42.7 vulnerable?

Maven · 15 releases from 42.7.0 to 42.7.14 · latest org.postgresql:postgresql is 42.7.14 · checked 18 Nov 2026

No known advisories in the last release

org.postgresql:postgresql 42.7.14, the last 42.7 release, has no known advisories. 4 advisories affect earlier 42.7.x releases, so update to 42.7.14.

Update within 42.7:mvn versions:use-dep-version -Dincludes=org.postgresql:postgresql -DdepVersion=42.7.14 -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

Fixed within 42.7.x, affecting earlier releases

  • HighCVE-2026-54291GHSA-j92g-9f8w-j86721 Jul 2026

    PostgreSQL JDBC Driver: Silent channel-binding authentication downgrade via unsupported certificate algorithms

    Affected
    >=42.7.4 <42.7.12
    Fixed in
    42.7.12
  • 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
  • HighCVE-2025-49146GHSA-hq9p-pm7w-8p5411 Jun 2025

    pgjdbc Client Allows Fallback to Insecure Authentication Despite channelBinding=require Configuration

    Affected
    >=42.7.4 <42.7.7
    Fixed in
    42.7.7
  • 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

Every org.postgresql:postgresql 42.7.x release

Affected: 42.7.0 to 42.7.11. 42.7.12 and later are not affected.

VersionKnown advisories
org.postgresql:postgresql 42.7.14None
org.postgresql:postgresql 42.7.13None
org.postgresql:postgresql 42.7.12None
org.postgresql:postgresql 42.7.11CVE-2026-54291
org.postgresql:postgresql 42.7.10CVE-2026-54291, CVE-2026-42198
org.postgresql:postgresql 42.7.9CVE-2026-54291, CVE-2026-42198
org.postgresql:postgresql 42.7.8CVE-2026-54291, CVE-2026-42198
org.postgresql:postgresql 42.7.7CVE-2026-54291, CVE-2026-42198
org.postgresql:postgresql 42.7.6CVE-2026-54291, CVE-2026-42198, CVE-2025-49146
org.postgresql:postgresql 42.7.5CVE-2026-54291, CVE-2026-42198, CVE-2025-49146
org.postgresql:postgresql 42.7.4CVE-2026-54291, CVE-2026-42198, CVE-2025-49146
org.postgresql:postgresql 42.7.3CVE-2026-42198
org.postgresql:postgresql 42.7.2CVE-2026-42198
org.postgresql:postgresql 42.7.1CVE-2026-42198, CVE-2024-1597
org.postgresql:postgresql 42.7.0CVE-2026-42198, CVE-2024-1597

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

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.