Vulnerability in org.postgresql:postgresql (CVE-2026-54291)
Summary
Vulnerability in org.postgresql:postgresql (CVE-2026-54291). Data can be tampered with by attackers. Exploitable via Ed25519. Mitigation: upgrade to 42.7.12 or later.
Original description
The description as published by the source.
pgjdbc is an open source postgresql JDBC Driver. In releases 42.7.4 through 42.7.11, channelBinding=require connections can be silently downgraded from SCRAM-SHA-256-PLUS with channel binding to plain SCRAM-SHA-256 without it, losing the man-in-the-middle protection the setting is meant to guarantee. An attacker who can intercept the TLS connection can trigger the downgrade with a certificate whose signature algorithm has no tls-server-end-point channel-binding hash, because the bundled com.ongres.scram:scram-client returns an empty byte array instead of failing and pgJDBC ScramAuthenticator checks only that the server advertised a PLUS mechanism, without rejecting the empty binding or checking that the negotiated mechanism uses channel binding. This issue is fixed in version 42.7.12.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54291 has been found in org.postgresql:postgresql.
Attackers can target a specific entry point like Ed25519 over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 5.9/10.
What to do: upgrade org.postgresql:postgresql to 42.7.12 or later.
If unsure, ask your IT team or search "org.postgresql:postgresql CVE-2026-54291" on the vendor's site.
CVE-2026-54291 (org.postgresql:postgresql) — CWE-636 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Ed25519 / Ed448 / ScramAuthenticator / prefer
Patched: 42.7.12 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-636) exists in org.postgresql:postgresql. Attackers reach the vulnerable code path via Ed25519 without authentication.
Check the vendor advisory for the affected versions of org.postgresql:postgresql. Attack surface: Ed25519 / Ed448 / ScramAuthenticator / prefer.
Severity: Medium (CVSS 5.9/10). Data can be tampered with by attackers.
Update to 42.7.12.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.postgresql:postgresql を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.postgresql:postgresql to 42.7.12ステージング環境で 42.7.12 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-54291 libpgjava
- Ubuntu UBUNTU-CVE-2026-54291 libpgjava
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- patch github.com
- web github.com
- web github.com