Quick answers
- Is CVE-2026-92899 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92899 being exploited in the wild.
- How severe is CVE-2026-92899?
- Medium severity, with a CVSS score of 4.8, published 30 September 2026.
- Which products and versions are affected?
- Apache WSS4J before 2.4.4, 3.0.x before 3.0.6, 4.0.x before 4.0.2.
- Is there a fix for CVE-2026-92899?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-92899 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-92899?
- Check whether you run Apache WSS4J at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in WSS4J's nonce replay cache, which keys entries on base64-encoded text rather than decoded bytes. Since the same byte sequence can be represented as valid base64 in multiple ways (e.g., with spaces), an attacker can alter the base64 encoding of a captured nonce to bypass the cache lookup. UsernameTokens with password digest authentication are vulnerable; tokens using plaintext passwords are unaffected. The fix changes the cache key to use decoded nonce bytes instead of base64 text.
Affected products
- Apache WSS4J before 2.4.4, 3.0.x before 3.0.6, 4.0.x before 4.0.2
Timeline
- 2026-09-30: disclosed