BlackTreeCVE Intelligencepgjdbc · pgjdbc
Official source article: GitHub GHSA-24RP-Q3W6-VC56 ↗. Check the applicable product and release in the original source.
Critical technical impact with a remotely reachable, unauthenticated path and a public exploit reference; no CISA KEV confirmation is currently recorded.
Alpine, Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Alpine v3.23v3.23 · community | java-postgresql-jdbc | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 42.6.2-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.22v3.22 · community | java-postgresql-jdbc | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 42.6.2-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.21v3.21 · community | java-postgresql-jdbc | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 42.6.2-r0 | Alpine Security Database ↗Source updated 19 Aug 2026 |
| Debian trixietrixie · source | libpgjava | Vendor fix publishedDebian records a fixed source-package version for this release. | 42.7.2-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian bookwormbookworm · source | libpgjava | Vendor fix publishedDebian records a fixed source-package version for this release. | 42.5.5-0+deb12u1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian forkyforky · source | libpgjava | Vendor fix publishedDebian records a fixed source-package version for this release. | 42.7.2-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian sidsid · source | libpgjava | Vendor fix publishedDebian records a fixed source-package version for this release. | 42.7.2-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| Mavenorg.postgresql:postgresql | ECOSYSTEM: introduced 0; fixed 42.2.28 | 42.2.28 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenorg.postgresql:postgresql | ECOSYSTEM: introduced 42.3.0; fixed 42.3.9 | 42.3.9 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenorg.postgresql:postgresql | ECOSYSTEM: introduced 42.4.0; fixed 42.4.4 | 42.4.4 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenorg.postgresql:postgresql | ECOSYSTEM: introduced 42.5.0; fixed 42.5.5 | 42.5.5 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenorg.postgresql:postgresql | ECOSYSTEM: introduced 42.6.0; fixed 42.6.1 | 42.6.1 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenorg.postgresql:postgresql | ECOSYSTEM: introduced 42.7.0; fixed 42.7.2 | 42.7.2 | OSV record ↗aggregator derived · 10 Sep 2026 |
| mavenorg.postgresql:postgresql | < 42.2.28 | 42.2.28 | GitHub advisory ↗upstream repository advisory · 21 Mar 2026 |
| mavenorg.postgresql:postgresql | >= 42.3.0, < 42.3.9 | 42.3.9 | GitHub advisory ↗upstream repository advisory · 21 Mar 2026 |
| mavenorg.postgresql:postgresql | >= 42.4.0, < 42.4.4 | 42.4.4 | GitHub advisory ↗upstream repository advisory · 21 Mar 2026 |
| mavenorg.postgresql:postgresql | >= 42.5.0, < 42.5.5 | 42.5.5 | GitHub advisory ↗upstream repository advisory · 21 Mar 2026 |
| mavenorg.postgresql:postgresql | >= 42.6.0, < 42.6.1 | 42.6.1 | GitHub advisory ↗upstream repository advisory · 21 Mar 2026 |
| mavenorg.postgresql:postgresql | >= 42.7.0, < 42.7.2 | 42.7.2 | GitHub advisory ↗upstream repository advisory · 21 Mar 2026 |
Critical technical impact with a remotely reachable, unauthenticated path and a public exploit reference; no CISA KEV confirmation is currently recorded.
Fix not verifiedpgjdbc, the PostgreSQL JDBC Driver, allows attacker to inject SQL if using PreferQueryMode=SIMPLE. Note this is not the default. In the default mode there is no vulnerability. A placeholder for a numeric value must be immediately preceded by a minus. There must be a second placeholder for a string value after the first placeholder; both must be on the same line. By constructing a matching string payload, the attacker can inject SQL to alter the query,bypassing the protections that parameterized queries bring against SQL Injection attacks. Versions before 42.7.2, 42.6.1, 42.5.5, 42.4.4, 42.3.9, and 42.2.28 are affected.
pgjdbc, the PostgreSQL JDBC Driver, allows attacker to inject SQL if using PreferQueryMode=SIMPLE. Note this is not the default. In the default mode there is no vulnerability. A placeholder for a numeric value must be immediately preceded by a minus. There must be a second placeholder for a string value after the first placeholder; both must be on the same line. By constructing a matching string payload, the attacker can inject SQL to alter the query,bypassing the protections that parameterized queries bring against SQL Injection attacks. Versions before 42.7.2, 42.6.1, 42.5.5, 42.4.4, 42.3.9, and 42.2.28 are affected.
Attacker-controlled data is not kept separate from SQL query syntax, allowing the intended database operation to be changed.
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
pgjdbc, the PostgreSQL JDBC Driver, allows attacker to inject SQL if using PreferQueryMode=SIMPLE. Note this is not the default. In the default mode there is no vulnerability. A placeholder for a numeric value must be immediately preceded by a minus. There must be a second placeholder for a string value after the first placeholder; both must be on the same line. By constructing a matching string payload, the attacker can inject SQL to alter the query,bypassing the protections that parameterized queries bring against SQL Injection attacks. Versions before 42.7.2, 42.6.1, 42.5.5, 42.4.4, 42.3.9, and 42.2.28 are affected.
Attacker-controlled data is not kept separate from SQL query syntax, allowing the intended database operation to be changed.
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
CISA Vulnrichment records proof-of-concept exploitation in its SSVC data. BlackTree has not independently executed or validated exploit material.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'). The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
Operational remediation based on structured source evidence.
Published 19 Feb 2024 · Last source change 3 Nov 2025, 21:52 UTC · CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Core structured fields are present and their contributing authorities are shown above.
No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.