Skip to content
Fencer Intel
medium 6.6

CVE-2025-59432 json

Timing Attack Vulnerability in SCRAM Authentication

published last yr. modified 29d ago also GHSA-3wfh-36rx-9537 , EUVD-2025-29670

cvss
6.6
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 53%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven com.ongres.scram:scram-common 3.2
  • libscram-java Debian 14 3.2-1

debian advisories DEBIAN-CVE-2025-59432

  • ongres-scram SLES for SAP applications 16.0, SLES 16.0 3.1-160000.3.1
  • ongres-scram SLE Module for Server Applications 15 SP7, SLE Module for Server Applications 15 SP6, openSUSE Leap 15.6 2.1-150400.8.5.1

suse advisories SUSE-SU-2025:21016-1SUSE-SU-2025:4054-1

  • ongres-scram openSUSE Leap 16.0 3.1-160000.3.1
  • ongres-scram openSUSE Tumbleweed 3.2-7.1

opensuse advisories openSUSE-SU-2025:20059-1openSUSE-SU-2025:15680-1

Is CVE-2025-59432 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-59432 updated cvss 6.8

ongres-scram: Timing Attack Vulnerability in SCRAM Authentication

  • Red Hat build of Apache Camel 4 for Quarkus 3 client, common Red Hat build of Quarkus client, common Red Hat Enterprise Linux 8 ongres-scram, ongres-scram-client Red Hat Enterprise Linux 9 ongres-scram, ongres-scram-client Red Hat Enterprise Linux 10 ongres-scram, postgresql-jdbc Red Hat JBoss Enterprise Application Platform 7 client, common
    +2 more products
    Red Hat JBoss Enterprise Application Platform 8 client, common Red Hat JBoss Enterprise Application Platform Expansion Pack client, common
    affected: workaround, no fix available “Fix deferred”
  • Red Hat build of Quarkus 3.20.5.redhat scram-common 3.2.0.redhat-00001
    fixed: vendor fix RHSA-2026:1899
  • Red Hat build of Quarkus 3.27.2.redhat scram-common 3.2.0.redhat-00001
    fixed: vendor fix RHSA-2026:1965
  • Red Hat build of Quarkus 3.20.5.redhat jna 5.8.0, lit 3.2.1, bson 5.3.1, db2 1.20.6, h2 2.3.230, y18n 5.0.8, +1015 more Red Hat build of Quarkus 3.27.2.redhat jna 5.8.0, bson 5.5.1, db2 1.21.4, h2 2.3.230, y18n 5.0.8, cliui 8.0.1, +1004 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.70% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 4.0 6.6 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:U
CNA 4.0 6.6 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected packages

ecosystem package affected fixed in
maven com.ongres.scram:scram-common
<3.2
3.2

Affected products

  • ongres scram

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.