Widely used pgJDBC library; TLS channel binding downgrade enables MITM on PostgreSQL connections.
CVE-2026-54291
pgJDBC 42.7.4–42.7.11 can downgrade TLS binding, removing MITM protection.
Is CVE-2026-54291 being exploited?
Not confirmed. CVE-2026-54291 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.24% probability of exploitation in the next 30 days.
How severe is CVE-2026-54291?
CVE-2026-54291 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-54291?
Yes. A fix has been recorded for CVE-2026-54291. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-54291 affect?
CVE-2026-54291 affects pgjdbc 42.7.4-42.7.11. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-54291?
Upgrade to pgjdbc 42.7.12 or later
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker intercepting TLS can downgrade to non-bound SCRAM, enabling MITM access to DB data.
Patch when possible
- affected>= 42.7.4 and < 42.7.12
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.