SCRAM (Salted Challenge Response Authentication Mechanism) is part of the family of Simple Authentication and Security Layer (SASL, RFC 4422) authentication mechanisms

Overview

SCRAM (Salted Challenge Response Authentication Mechanism) is part of the family of Simple Authentication and Security Layer (SASL, RFC 4422) authentication mechanisms. Prior to version 3.2, a timing attack vulnerability exists in the SCRAM Java implementation. The issue arises because Arrays.equals was used to compare secret values such as client proofs and server signatures. Since Arrays.equals performs a short-circuit comparison, the execution time varies depending on how many leading bytes match. This behavior could allow an attacker to perform a timing side-channel attack and potentially infer sensitive authentication material. All users relying on SCRAM authentication are impacted. This vulnerability has been patched in version 3.1 by replacing Arrays.equals with MessageDigest.isEqual, which ensures constant-time comparison.

Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.

Vendor advisories

• RHSA-2026:1899 · Red Hat · fixed in: Red Hat build of Quarkus 3.20.5.redhat · released 2026-02-05 · advisory
• RHSA-2026:1965 · Red Hat · fixed in: Red Hat build of Quarkus 3.27.2.redhat · released 2026-02-05 · advisory
• Red Hat VEX · Moderate · affected: Red Hat build of Apache Camel 4 for Quarkus 3, Red Hat build of Quarkus, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9, Red Hat JBoss Enterprise Application Platform 7, … · no fix planned: Red Hat build of Apache Camel 4 for Quarkus 3, Red Hat build of Quarkus, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8, … · updated 2026-10-20 · vex