VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

libpgjava: vulnerability history, versions and safety

libpgjava is a package in the Debian ecosystem. Vulert records 17 vulnerabilities for it across 39 releases, from Aug 2018 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
17 vulnerabilities recorded U17
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
2 in the last 12 months

Most recent disclosure 06 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all libpgjava vulnerabilities

Vulert verdict on libpgjava i

Updated on 22 Oct 2026

Careful: 2 of the 17 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 17 vulnerabilities on record across 7 years, 2 in the last year.

What to do: Plan around the 2 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 17 over 7 years · 2 in the last year i
  • Latest disclosure 06 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 2 i

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 holds for libpgjava, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 39 of 39 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 2
  • 2020 2
  • 2022 8
  • 2024 3
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for libpgjava

The 5 most severe of 17 vulnerabilities recorded for this package

Search all 17 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
Critical Code Execution Vulnerability in PostgreSQL JDBC Driver (libpgjava) 9.8 critical 42.2.15-1+deb11u1 02 Feb 2022
Arbitrary File Write Vulnerability in libpgjava Package 9.8 critical 42.2.15-1+deb11u1 10 Mar 2022
CVE-2024-1597: PostgreSQL JDBC Driver SQL Injection Vulnerability 9.8 critical 42.2.15-1+deb11u2 19 Feb 2024
SSL Host Name Verification Bypass in libpgjava - CVE-2018-10936 8.1 high 42.2.5-1 30 Aug 2018
SQL Injection Vulnerability in PostgreSQL JDBC Driver (libpgjava) - CVE-2022-31197 8.0 high 42.2.15-1+deb11u2 03 Aug 2022

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 libpgjava

Is libpgjava safe to use?

Vulert records 17 vulnerabilities for libpgjava in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 17 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does libpgjava have?

17 vulnerabilities are recorded for libpgjava in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 17 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new libpgjava vulnerabilities disclosed?

2 vulnerabilities were recorded for libpgjava in the last 12 months, and the oldest entry in this database dates to 30 Aug 2018. 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 libpgjava 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 libpgjava for upcoming vulnerabilities?

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