Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Wed, 30 Sep 2026 14:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Apache
Apache wss4j |
|
| Vendors & Products |
Apache
Apache wss4j |
Wed, 30 Sep 2026 13:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-290 | |
| References |
| |
| Metrics |
cvssV3_1
|
Wed, 30 Sep 2026 12:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Apache WSS4J: UsernameToken replay protection bypassed by re-encoding the Nonce | |
| References |
|
Status: PUBLISHED
Assigner: apache
Published:
Updated: 2026-09-30T12:49:57.226Z
Reserved: 2026-09-17T10:21:29.052Z
Link: CVE-2026-92899
Updated: 2026-09-30T12:12:25.397Z
Status : Awaiting Analysis
Published: 2026-09-30T13:17:21.823
Modified: 2026-09-30T16:14:10.347
Link: CVE-2026-92899
No data.
OpenCVE Enrichment
Updated: 2026-09-30T14:30:18Z