CVE-2026-92899 Affecting wss4j package, versions *


Severity

Recommended
low

Based on Debian security rating.

Threat Intelligence

EPSS
0.51% (42nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIAN12-WSS4J-20342691
  • published1 Oct 2026
  • disclosed30 Sept 2026

Introduced: 30 Sep 2026

NewCVE-2026-92899  (opens in a new tab)

How to fix?

There is no fixed version for Debian:12 wss4j.

NVD Description

Note: Versions mentioned in the description apply only to the upstream wss4j package and not the wss4j package as distributed by Debian. See How to fix? for Debian:12 relevant fixed versions and status.

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.