CyberSecBulletin
CVE-2026-97468NVD status: Analyzed

Apache CXF: Use of Weak Hash

Published Updated By the CyberSecBulletin desk

CVE-2026-97468 is a critical-severity use of weak hash vulnerability in Apache CXF from Apache, with a CVSS 3.1 base score of 9.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 4.2.4, 4.1.9, 3.6.13 as the first without the flaw, so updating Apache CXF to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.22% chance of exploitation within 30 days, which is low compared with other CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update Apache CXF to 4.2.4 or 4.1.9 or 3.6.13, whichever matches your release line, or a later version.
  2. Update Cxf to 3.6.13 or 4.1.9 or 4.2.4, whichever matches your release line, or a later version.
  3. Read the advisory on lists.apache.org for workarounds and exact fixed builds.
  4. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
ApacheApache CXF4.2.0 up to, but not including, 4.2.4; 4.0.0 up to, but not including, 4.1.9; before 3.6.134.2.4, 4.1.9, 3.6.13
ApacheCxfbefore 3.6.13; 4.0.0 up to, but not including, 4.1.9; 4.2.0 up to, but not including, 4.2.43.6.13, 4.1.9, 4.2.4

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N. Scored by CISA (ADP).

Official description

Apache CXF's STSTokenValidator and Security Token Service (STS) cached validated security tokens under a non-cryptographic 32-bit hash of the token (Java Arrays.hashCode/hashCode()), and treated a cache hit as proof that the presented token had already been validated. An attacker could craft a token (for example a UsernameToken or a self-signed SAML Assertion) whose hash collides with a cached entry. The token would then be accepted without password validation, signature trust verification or a call to the STS. This could let the attacker authenticate as another user and, through STS token validation or renewal, obtain STS-signed tokens for that identity. Users are recommended to upgrade to versions 4.2.4 or 4.1.9 or 3.6.13, which fix this issue.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Use of Weak Hash

The product uses an algorithm that produces a digest (output value) that does not meet security expectations for a hash function that allows an adversary to reasonably determine the original input (preimage attack), find another input that can produce the same hash (2nd preimage attack), or find multiple inputs that evaluate to the same hash (birthday attack).

More Use of Weak Hash vulnerabilities (CWE-328)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Other vulnerabilities in Apache CXF

All Apache CXF vulnerabilities

Recent Use of Weak Hash vulnerabilities

Spotted an error? Tell us.