Quick answers
- Is CVE-2026-85532 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-85532 being exploited in the wild.
- How severe is CVE-2026-85532?
- Informational severity, published 30 September 2026.
- Which products and versions are affected?
- Apache WSS4J before 4.0.2, before 3.0.6, before 2.4.4.
- Is there a fix for CVE-2026-85532?
- 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-85532 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-85532?
- 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
WSS4J's key derivation function failed to enforce bounds on attacker-controlled derived-key length and offset parameters, allowing values outside the safe ranges (length < 16 bytes or > 512 bytes, offset > 4096 bytes). This enables generation of cryptographically weak keys or triggering resource exhaustion. The vulnerability is fixed in versions 4.0.2, 3.0.6, and 2.4.4 by enforcing strict bounds checking.
Affected products
- Apache WSS4J before 4.0.2, before 3.0.6, before 2.4.4
Timeline
- 2026-09-30: disclosed