Vulnerability in com.ongres.scram:scram-client (CVE-2026-53712)
Summary
Vulnerability in com.ongres.scram:scram-client (CVE-2026-53712). Risk of unauthorized operations or information disclosure. Exploitable via TlsServerEndpoint. Mitigation: upgrade to 3.3 or later.
Original description
The description as published by the source.
SCRAM (Salted Challenge Response Authentication Mechanism) is part of the family of Simple Authentication and Security Layer (SASL, RFC 4422) authentication mechanisms. Prior to 3.3, a flaw in com.ongres.scram:scram-client and com.ongres.scram:scram-common allows an attacker capable of a TLS man-in-the-middle attack to silently downgrade a connection from SCRAM-SHA-256-PLUS with channel binding to standard SCRAM-SHA-256 without channel binding when TlsServerEndpoint processes an X.509 certificate using a modern signature algorithm such as Ed25519; getChannelBindingData() can return an empty byte array after NoSuchAlgorithmException, and the ScramClient builder treats that as absent channel-binding data. This issue is fixed in version 3.3.
Source: GitHub Security Advisories (Global) 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-53712 has been found in com.ongres.scram:scram-client.
Attackers can target a specific entry point like TlsServerEndpoint over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade com.ongres.scram:scram-client to 3.3 or later.
If unsure, ask your IT team or search "com.ongres.scram:scram-client CVE-2026-53712" on the vendor's site.
CVE-2026-53712 (com.ongres.scram:scram-client) — CWE-636
Attack surface: TlsServerEndpoint / X.509 / WITH / Ed25519
Patched: 3.3 — 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 com.ongres.scram:scram-client. Attackers reach the vulnerable code path via TlsServerEndpoint.
Check the vendor advisory for the affected versions of com.ongres.scram:scram-client. Attack surface: TlsServerEndpoint / X.509 / WITH / Ed25519.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 3.3.
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・依存マニフェストで com.ongres.scram:scram-client を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade com.ongres.scram:scram-client to 3.3ステージング環境で 3.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com