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.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Exploit likelihood
What each source reports
CVE List Score used
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.
- Record
CVE-2026-85532- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-20
- Updated
- 2026-11-02
EUVDEUVD-2026-89791
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.
- Record
EUVD-2026-89791- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-5x6j-m6jc-q2r5No score
Apache WSS4J accepted attacker-controlled derived-key lengths and offsets without adequate bounds...
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.
- Record
GHSA-5x6j-m6jc-q2r5- Weakness
- CWE-20
- Updated
- 2026-11-02
NVD
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.
- Record
CVE-2026-85532- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-20
- Updated
- 2026-11-02
OSVDEBIAN-CVE-2026-85532
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.
- Record
DEBIAN-CVE-2026-85532- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVUBUNTU-CVE-2026-85532
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.
- Record
UBUNTU-CVE-2026-85532- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVCLSA-2026-1794358887No score
TuxCare security update for org.apache.wss4j (1 CVE)
TuxCare rebuilt 10 org.apache.wss4j packages to address 1 CVE. Fixed in 2.4.3-tuxcare.2.
- Record
CLSA-2026-1794358887- Updated
- 2026-11-11
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
org.apache.wss4j:wss4jTuxCare:Maven | 2.4.3 up to 2.4.3-tuxcare.2, plus listed versions 2.4.3-tuxcare.1 | 2.4.3-tuxcare.2 |
org.apache.wss4j:wss4j-bindingsTuxCare:Maven | 2.4.3 up to 2.4.3-tuxcare.2, plus listed versions 2.4.3-tuxcare.1 | 2.4.3-tuxcare.2 |
org.apache.wss4j:wss4j-integrationTuxCare:Maven | 2.4.3 up to 2.4.3-tuxcare.2, plus listed versions 2.4.3-tuxcare.1 | 2.4.3-tuxcare.2 |
org.apache.wss4j:wss4j-parentTuxCare:Maven | 2.4.3 up to 2.4.3-tuxcare.2, plus listed versions 2.4.3-tuxcare.1 | 2.4.3-tuxcare.2 |
org.apache.wss4j:wss4j-policyTuxCare:Maven | 2.4.3 up to 2.4.3-tuxcare.2, plus listed versions 2.4.3-tuxcare.1 | 2.4.3-tuxcare.2 |
org.apache.wss4j:wss4j-ws-security-commonTuxCare:Maven | 2.4.3 up to 2.4.3-tuxcare.2, plus listed versions 2.4.3-tuxcare.1 | 2.4.3-tuxcare.2 |
org.apache.wss4j:wss4j-ws-security-domTuxCare:Maven | 2.4.3 up to 2.4.3-tuxcare.2, plus listed versions 2.4.3-tuxcare.1 | 2.4.3-tuxcare.2 |
org.apache.wss4j:wss4j-ws-security-policy-staxTuxCare:Maven | 2.4.3 up to 2.4.3-tuxcare.2, plus listed versions 2.4.3-tuxcare.1 | 2.4.3-tuxcare.2 |
org.apache.wss4j:wss4j-ws-security-staxTuxCare:Maven | 2.4.3 up to 2.4.3-tuxcare.2, plus listed versions 2.4.3-tuxcare.1 | 2.4.3-tuxcare.2 |
org.apache.wss4j:wss4j-ws-security-webTuxCare:Maven | 2.4.3 up to 2.4.3-tuxcare.2, plus listed versions 2.4.3-tuxcare.1 | 2.4.3-tuxcare.2 |
Show 10 moreShow less
| Package | Affected | Fixed |
|---|---|---|
wss4jDebian:12 | All versions, plus listed versions 1.6.19-31.6.19-4 | None known |
wss4jDebian:13 | All versions, plus listed versions 1.6.19-4 | None known |
wss4jDebian:14 | All versions, plus listed versions 1.6.19-4 | None known |
wss4jUbuntu:16.04:LTS | All versions, plus listed versions 1.6.15-2 | None known |
wss4jUbuntu:18.04:LTS | All versions, plus listed versions 1.6.19-1 | None known |
wss4jUbuntu:20.04:LTS | All versions, plus listed versions 1.6.19-2 | None known |
wss4jUbuntu:22.04:LTS | All versions, plus listed versions 1.6.19-2 | None known |
wss4jUbuntu:24.04:LTS | All versions, plus listed versions 1.6.19-3 | None known |
wss4jUbuntu:26.10 | All versions, plus listed versions 1.6.19-4build1 | None known |
wss4jUbuntu:26.04:LTS | All versions, plus listed versions 1.6.19-41.6.19-4build1 | None known |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, aliases, facts | OSV | |
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2026-85532 is a high vulnerability (CVSS 7.5) in Apache Wss4j, published September 30, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.55%, the 46th percentile. Fixed in org.apache.wss4j:wss4j 2.4.3-tuxcare.2.
References
lists.apache.org/thread.html/7jllcpbf4nbzhdp2vchz5yplnl5w6vd6
openwall.com/lists/oss-security/2026/09/30/8
nvd.nist.gov/vuln/detail/CVE-2026-85532
github.com/advisories/GHSA-5x6j-m6jc-q2r5
security-tracker.debian.org/tracker/CVE-2026-85532
ubuntu.com/security/CVE-2026-85532
cve.org/CVERecord?id=CVE-2026-85532