CVE-2026-54291

MEDIUMNVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.9 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 84% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 4 sources updated this week
5.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.9Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.9
EG Score
5.9(medium)
EPSS
14.6%
KEV
Not listed

Published

July 6, 2026

Last Modified

July 9, 2026

Advisory Details (3)

Auto-updated Jul 6, 2026
Patch available. Sources: github_release, github_commit, github.
github Patch Available

Silent channel-binding authentication downgrade via unsupported certificate algorithms · Advisory · pgjdbc/pgjdbc · GitHub

https://github.com/pgjdbc/pgjdbc/security/advisories/GHSA-j92g-9f8w-j867
github_commit Patch Available

commit 77df98e4e66c (pgjdbc/pgjdbc)

Patch available: pgjdbc/pgjdbc REL42.7.12 (contains commit 77df98e4e66c)

https://github.com/pgjdbc/pgjdbc/commit/77df98e4e66c12936ded3478a0954f6f580bad99
github_release Patch Available

SCRAM Java 3.3

Patch available: ongres/scram 3.3

https://github.com/ongres/scram/releases/tag/3.3

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 19× in last 7d / 19× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-10 23:58 UTCEG score recompute
  4. 2026-07-09 23:11 UTCEG score recompute▼ 2.30
  5. 2026-07-09 19:10 UTCEPSS rescore
  6. 2026-07-09 19:10 UTCEPSS rescore
  7. 2026-07-09 13:52 UTCNVD updateCVSS v3 → 5.9 · severity → MEDIUM
  8. 2026-07-09 12:18 UTCEG score recompute
  9. 2026-07-09 01:27 UTCEG score recompute
  10. 2026-07-08 15:16 UTCEPSS rescore
  11. 2026-07-08 15:16 UTCEPSS rescore
  12. 2026-07-08 14:34 UTCEG score recompute
  13. 2026-07-08 03:42 UTCEG score recompute
  14. 2026-07-07 16:51 UTCEG score recompute
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-07 13:46 UTCEPSS rescore
  17. 2026-07-07 06:00 UTCEG score recompute
  18. 2026-07-06 19:07 UTCEG score recompute
  19. 2026-07-06 19:06 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-54291?
CVE-2026-54291 is a medium vulnerability published on July 6, 2026. 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…
When was CVE-2026-54291 disclosed?
CVE-2026-54291 was first published in the National Vulnerability Database on July 6, 2026, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54291 actively exploited?
CVE-2026-54291 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 14.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54291?
CVE-2026-54291 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-54291?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54291, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-54291

Explore →

Is Your Infrastructure Affected by CVE-2026-54291?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs