CVE-2026-92899Apache WSS4J: UsernameToken replay protection bypassed by re-encoding the Nonce

Official 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.

Affected packages & fixed versions

Affected products (as reported)

References

• https://lists.apache.org/thread.html/nrzngsz1xm2lztq3t873663xx9wnrwm7 vendor-advisory
• http://www.openwall.com/lists/oss-security/2026/09/30/13