CVE-2026-85532: Apache WSS4J: Insufficient Validation of Derived-Key Parameters
Apache WSS4J accepted attacker-controlled derived-key lengths and offsets without adequate bounds. This could permit cryptographically weak keys or excessive CPU and memory consumption when processing crafted WS-Security messages. The fixes enforce a minimum key length of 16 bytes, a maximum length of 512 bytes, and a maximum offset of 4096 bytes. Users are recommended to upgrade to versions 4.0.2 or 3.0.6 or 2.4.4, which fix this issue.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Apache WSS4Jto a version that resolves this vulnerability.Fixed in 4.0.2 - Upgrade
Upgrade
Apache WSS4Jto a version that resolves this vulnerability.Fixed in 3.0.6 - Upgrade
Upgrade
Apache WSS4Jto a version that resolves this vulnerability.Fixed in 2.4.4
Event History
Frequently Asked Questions
What message processing paths are exposed to this issue?
Any Apache WSS4J deployment that processes crafted WS-Security messages containing attacker-controlled derived-key parameters may be exposed. The issue is triggered during processing of those parameters.
What must an attacker be able to do to exploit this?
An attacker needs to supply a crafted WS-Security message with derived-key lengths or offsets outside safe bounds. The malformed values can lead to weak derived keys or excessive CPU and memory consumption.
What parameter limits are enforced by the fix?
The fix requires a derived-key length of at least 16 bytes and no more than 512 bytes, and limits the derived-key offset to 4096 bytes.
Which versions contain the fix?
Upgrade to Apache WSS4J version 4.0.2, 3.0.6, or 2.4.4.