CVE-2026-92899 Apache WSS4J: UsernameToken replay protection bypassed by re-encoding the Nonce
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- No known exploitation · automatable: no · technical impact: partial
- Technology
- UbuntuDebianRed Hat
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.
Upgrade path
10 packages: 2 fixed, 8 with no fix yet.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| debian/wss4j(Debian 12) | = 1.6.19-3; = 1.6.19-4; All versions | No fix listed | No fix yet |
| debian/wss4j(Debian 13) | = 1.6.19-4; All versions | No fix listed | No fix yet |
| debian/wss4j(Debian 14) | = 1.6.19-4; All versions | No fix listed | No fix yet |
| redhat/wss4j(Red Hat camel_spring_boot 4) | All versions | No fix listed | No fix yet |
| ubuntu/wss4j(Ubuntu 22.04) | All versions | No fix listed | No fix yet |
| ubuntu/wss4j(Ubuntu 24.04) | All versions | No fix listed | No fix yet |
| ubuntu/wss4j(Ubuntu 26.04) | All versions | No fix listed | No fix yet |
| ubuntu/wss4j(Ubuntu 26.10) | All versions | No fix listed | No fix yet |
| apache wss4j | < 2.4.4; >= 3.0.0, < 3.0.6; >= 4.0.0, < 4.0.2 | 2.4.4, 3.0.6, 4.0.2 | Fixed |
| org.apache.wss4j/wss4j-ws-security-dom(Maven) | < 2.4.4; >= 3.0.0, < 3.0.6; >= 4.0.0, < 4.0.2 | 2.4.4, 3.0.6, 4.0.2 | Fixed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| org.apache.wss4j/wss4j-ws-security-dom(Maven) | >= 4.0.0, < 4.0.2 | 4.0.2 |
| org.apache.wss4j/wss4j-ws-security-dom(Maven) | >= 3.0.0, < 3.0.6 | 3.0.6 |
| org.apache.wss4j/wss4j-ws-security-dom(Maven) | < 2.4.4 | 2.4.4 |
| redhat/wss4j(Red Hat:camel_spring_boot:4) | All versions | No fix listed |
| redhat/wss4j(Red Hat:jboss_fuse:7) | All versions | No fix listed |
| redhat/wss4j(Red Hat:jboss_enterprise_application_platform:7) | All versions | No fix listed |
| debian/wss4j(Debian:12) | All versions | No fix listed |
| debian/wss4j(Debian:12) | = 1.6.19-3 | No fix listed |
| debian/wss4j(Debian:12) | = 1.6.19-4 | No fix listed |
| debian/wss4j(Debian:13) | All versions | No fix listed |
| debian/wss4j(Debian:13) | = 1.6.19-4 | No fix listed |
| debian/wss4j(Debian:14) | All versions | No fix listed |
| debian/wss4j(Debian:14) | = 1.6.19-4 | No fix listed |
| ubuntu/wss4j(Ubuntu:22.04) | All versions | No fix listed |
| ubuntu/wss4j(Ubuntu:24.04) | All versions | No fix listed |
| ubuntu/wss4j(Ubuntu:26.04) | All versions | No fix listed |
| ubuntu/wss4j(Ubuntu:26.10) | All versions | No fix listed |
| apache wss4j | < 2.4.4 | 2.4.4 |
| apache wss4j | >= 3.0.0, < 3.0.6 | 3.0.6 |
| apache wss4j | >= 4.0.0, < 4.0.2 | 4.0.2 |
References
- lists.apache.org mailing-list vendor-advisory
- www.openwall.com mailing-list third-party-advisory
- Red Hat CVE page vendor-advisory
- Red Hat Bugzilla 2543904 issue-tracking
- www.cve.org
- nvd.nist.gov
- Debian Security Tracker CVE-2026-92899 vendor-advisory
- Ubuntu CVE tracker vendor-advisory
- bugs.debian.org issue-tracking
- ENISA EUVD EUVD-2026-89798 third-party-advisory