CVE-2026-92899

Medium

Description

Apache WSS4J remembers the Nonce of each UsernameToken it accepts, so a captured token cannot be reused. It stored the Nonce as raw base64 text, but authentication decodes that text and uses the bytes.The same bytes can be written as base64 in several ways. An attacker who captured an authenticated request could re-send it with a space added to the Nonce: the password digest still verified, but the token no longer matched the remembered one, so the replay was accepted. Since a UsernameToken does not cover the message body, the captured token could then be reused on requests of the attacker's choosing until it expired. Affects deployments with a nonce replay cache configured, as Apache CXF has by default, and only tokens using a password digest. The cache is now keyed on the decoded Nonce. Users are recommended to upgrade to versions 4.0.2 or 3.0.6 or 2.4.4, which fix this issue.

SeverityMedium
CVSS4.8
Exploit probability—
ProductApache Wss4j
PublishedSep 30, 2026
First seenSep 30, 2026
Weakness typeCWE-290CWE-290

How to fix

Update
  • apache wss4j2.4.4, 3.0.6, 4.0.2 or later

Affected products

ProductAffected versionsFixed in
apache wss4jv < 2.4.4, 3.0.0 ≤ v < 3.0.6, 4.0.0 ≤ v < 4.0.22.4.4, 3.0.6, 4.0.2

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.