CVE-2026-92899

published 30 Sep 2026 · updated 6 Nov 2026

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

4.8MediumCVSS 4.8EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in WSS4J 2.4.4, WSS4J 3.0.6, WSS4J 4.0.2 and 3 more.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
ApacheWSS4J<2.4.4, >=3.0.0 <3.0.6, >=4.0.0 <4.0.22.4.4, 3.0.6, 4.0.2
Apache Software Foundation<2.4.4, >=3.0.0 <3.0.6, >=4.0.0 <4.0.22.4.4, 3.0.6, 4.0.2

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Apache, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-92899 severity on Zeptric[![CVE-2026-92899](https://zeptric.io/badge/cve/CVE-2026-92899.svg)](https://zeptric.io/cve/CVE-2026-92899)