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.
References
| Link | Resource |
|---|---|
| https://lists.apache.org/thread.html/nrzngsz1xm2lztq3t873663xx9wnrwm7 | Mailing List Vendor Advisory |
| http://www.openwall.com/lists/oss-security/2026/09/30/13 | Mailing List Third Party Advisory |
Configurations
Configuration 1 (hide)
|
History
02 Oct 2026, 20:18
| Type | Values Removed | Values Added |
|---|---|---|
| CPE | cpe:2.3:a:apache:wss4j:*:*:*:*:*:*:*:* | |
| References | () https://lists.apache.org/thread.html/nrzngsz1xm2lztq3t873663xx9wnrwm7 - Mailing List, Vendor Advisory | |
| References | () http://www.openwall.com/lists/oss-security/2026/09/30/13 - Mailing List, Third Party Advisory | |
| First Time |
Apache
Apache wss4j |
30 Sep 2026, 13:17
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-09-30 13:17
Updated : 2026-10-02 20:18
NVD link : CVE-2026-92899
Mitre link : CVE-2026-92899
CVE.ORG link : CVE-2026-92899
JSON object : View
Products Affected
apache
- wss4j
CWE
CWE-290
Authentication Bypass by Spoofing
