Skip to content

Apache WSS4J: authentication bypass by spoofing

Medium4.8CVE-2026-92899 · Published Sep 30, 2026 · updated Oct 2, 2026

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 versions

PackageAffectedFixed in
Apache WSS4J
Product
>= 4.0.0, < 4.0.24.0.2
>= 3.0.0, < 3.0.63.0.6
< 2.4.42.4.4
Details and references

More Apache Software Foundation advisories

All Apache Software Foundation
Advisory
Apache WSS4J: integer overflow
High7.5Sep 30
Apache WSS4J: insufficient authenticity check
Critical9.1Sep 30
Apache WSS4J: protection mechanism failure
High7.5Sep 30
Apache WSS4J: expression injection
Critical9.1Sep 30
Apache WSS4J: authentication bypass
Critical9.8Sep 30
Apache WSS4J: resource exhaustion
High7.5Sep 30

Critical advisories by email

Wednesdays: the week’s critical and high advisories in the AI and data stack, with the fixed versions. Only in weeks that have some.

Double opt-in. Unsubscribe any time.