CVE-2026-92899
MEDIUMDescription
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.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
Exploit Intelligence
Moderate risk: more likely to be exploited than 42% of all known CVEs.
References
Related Vulnerabilities
Other CWE-290 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2024-4358 | Critical | 9.8 | 97% | KEV | - |
| CVE-2022-24112 | Critical | 9.8 | 96% | KEV | Fix |
| CVE-2022-23131 | Critical | 9.1 | 96% | KEV | - |
| CVE-2021-29441 | High | 8.6 | 83% | - | Fix |
| CVE-2019-1234 | High | 7.5 | 75% | - | - |
| CVE-2021-31195 | Medium | 6.5 | 74% | - | Fix |
Common questions
How do I fix CVE-2026-92899?
Upgrade wss4j to 4.0.2 or later.
Is CVE-2026-92899 being actively exploited?
Not that we know of. CVE-2026-92899 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.51% is the estimated probability that it will be exploited in the next 30 days. That is higher than 42% of all scored CVEs.
How severe is CVE-2026-92899?
CVE-2026-92899 has a CVSS v3 base score of 4.8, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-92899 affect?
Published advisories record a fix for wss4j (NVD). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-92899
Markdown
[](https://tridentstack.com/cve/CVE-2026-92899)HTML
<a href="https://tridentstack.com/cve/CVE-2026-92899"><img src="https://tridentstack.com/cve/badge/CVE-2026-92899.svg" alt="CVE-2026-92899"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-02.