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.2%, top 85% 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
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.9MEDIUMmedium confidence
EG Risk
27
EG Risk 27/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity59% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.2%
EPSS %ILE
13th
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.
githubMentions a patch (unverified)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatpostgresql2026-08-13redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
libpgjava42.2.15-1 ... 42.7.9-1 (39 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libpgjava42.5.4-1 ... 42.7.9-1 (21 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libpgjava42.7.10-1 ... 42.7.9-1 (9 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libpgjava42.7.10-1 ... 42.7.9-1 (7 versions)
  • every version up to 42.7.12-1: fixed in 42.7.12-1
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.postgresql:postgresql42.7.10 ... 42.7.9 (8 versions)
  • 42.7.4 up to 42.7.12: fixed in 42.7.12
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 32× 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.

Showing the most recent 100 of 144 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:26 UTCEPSS rescore
  8. 2026-10-02 17:56 UTCEPSS rescore
  9. 2026-10-01 19:50 UTCEPSS rescore
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-29 15:22 UTCEPSS rescore
  12. 2026-09-28 13:51 UTCEPSS rescore
  13. 2026-09-27 13:48 UTCEPSS rescore
  14. 2026-09-26 15:59 UTCEPSS rescore
  15. 2026-09-24 14:04 UTCEPSS rescore
  16. 2026-09-23 17:54 UTCEPSS rescore
  17. 2026-09-23 06:23 UTCEG score recompute
  18. 2026-09-23 06:23 UTCVendor advisory
  19. 2026-09-20 20:16 UTCEPSS rescore
  20. 2026-09-18 19:28 UTCEPSS rescore
  21. 2026-09-18 05:59 UTCEG score recompute
  22. 2026-09-18 05:59 UTCVendor advisory
  23. 2026-09-17 19:31 UTCEPSS rescore
  24. 2026-09-16 14:08 UTCEPSS rescore
  25. 2026-09-16 05:15 UTCEPSS rescore
Show 75 more
  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-13 14:23 UTCEG score recompute
  3. 2026-09-13 14:23 UTCVendor advisory
  4. 2026-09-12 13:37 UTCEG score recompute
  5. 2026-09-12 13:37 UTCVendor advisory
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-10 09:35 UTCEPSS rescore
  8. 2026-09-08 22:01 UTCEPSS rescore
  9. 2026-09-07 16:01 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-05 23:11 UTCEG score recompute
  12. 2026-09-05 23:11 UTCVendor advisory
  13. 2026-09-04 05:06 UTCEPSS rescore
  14. 2026-09-02 14:12 UTCEPSS rescore
  15. 2026-09-01 13:54 UTCEPSS rescore
  16. 2026-09-01 04:40 UTCEPSS rescore
  17. 2026-08-30 19:17 UTCEPSS rescore
  18. 2026-08-30 08:14 UTCEG score recompute
  19. 2026-08-30 08:14 UTCVendor advisory
  20. 2026-08-30 01:22 UTCEPSS rescore
  21. 2026-08-28 21:41 UTCEPSS rescore
  22. 2026-08-27 21:58 UTCEG score recompute
  23. 2026-08-27 21:58 UTCVendor advisory
  24. 2026-08-27 14:25 UTCEPSS rescore
  25. 2026-08-26 14:46 UTCEPSS rescore
  26. 2026-08-26 13:55 UTCVendor advisory
  27. 2026-08-24 20:48 UTCEG score recompute
  28. 2026-08-24 20:48 UTCVendor advisory
  29. 2026-08-23 18:47 UTCEG score recompute
  30. 2026-08-23 18:47 UTCVendor advisory
  31. 2026-08-23 00:19 UTCEPSS rescore
  32. 2026-08-22 18:01 UTCEG score recompute
  33. 2026-08-22 18:01 UTCVendor advisory
  34. 2026-08-21 23:49 UTCEPSS rescore
  35. 2026-08-21 17:03 UTCEG score recompute
  36. 2026-08-21 17:03 UTCVendor advisory
  37. 2026-08-20 22:55 UTCEPSS rescore
  38. 2026-08-20 15:48 UTCEG score recompute
  39. 2026-08-20 15:48 UTCVendor advisory
  40. 2026-08-19 17:04 UTCEPSS rescore
  41. 2026-08-19 12:30 UTCEG score recompute
  42. 2026-08-19 12:30 UTCVendor advisory
  43. 2026-08-18 13:48 UTCEPSS rescore
  44. 2026-08-18 10:58 UTCEG score recompute
  45. 2026-08-18 10:58 UTCVendor advisory
  46. 2026-08-17 13:47 UTCEPSS rescore
  47. 2026-08-17 09:24 UTCEG score recompute
  48. 2026-08-17 09:24 UTCVendor advisory
  49. 2026-08-16 14:56 UTCEPSS rescore
  50. 2026-08-16 08:38 UTCEG score recompute
  51. 2026-08-16 08:38 UTCVendor advisory
  52. 2026-08-16 02:14 UTCEPSS rescore
  53. 2026-08-15 07:52 UTCEG score recompute
  54. 2026-08-15 07:52 UTCVendor advisory
  55. 2026-08-15 01:30 UTCEPSS rescore
  56. 2026-08-14 06:11 UTCVendor advisory
  57. 2026-08-13 05:24 UTCEG score recompute
  58. 2026-08-12 13:51 UTCEPSS rescore
  59. 2026-08-12 04:38 UTCEG score recompute
  60. 2026-08-11 03:40 UTCEG score recompute
  61. 2026-08-11 00:00 UTCEPSS rescore
  62. 2026-08-10 02:54 UTCEG score recompute
  63. 2026-08-09 13:46 UTCEPSS rescore
  64. 2026-08-09 02:08 UTCEG score recompute
  65. 2026-08-08 16:37 UTCEPSS rescore
  66. 2026-08-08 01:22 UTCEG score recompute
  67. 2026-08-07 00:37 UTCEG score recompute
  68. 2026-08-06 13:47 UTCEPSS rescore
  69. 2026-08-05 23:50 UTCEG score recompute
  70. 2026-08-05 19:17 UTCEPSS rescore
  71. 2026-08-04 23:05 UTCEG score recompute
  72. 2026-08-04 15:10 UTCEPSS rescore
  73. 2026-08-04 10:39 UTCEPSS rescore
  74. 2026-08-03 22:18 UTCEG score recompute
  75. 2026-08-03 10:36 UTCEPSS rescore

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 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 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
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?
A fix for CVE-2026-54291 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54291 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.