Apache WSS4J vulnerabilities

12 CVEs affecting Apache WSS4J, 0 known to be exploited (CISA KEV), with EPSS scores. Latest: CVE-2026-95616, published 2026-09-30.

Highest priority

Known exploited (CISA KEV) first, then by EPSS exploit probability.

CVE-2020-13936, published 2021-03-10. High severity, CVSS 8.8. EPSS: 22.7% chance of exploitation in the next 30 days. An attacker that is able to modify Velocity templates may execute arbitrary Java code or run arbitrary system commands with the same privileges as the account running the Servlet container. This…
CVE-2014-3623, published 2014-10-30. Medium severity, CVSS 5.0. EPSS: 9.2% chance of exploitation in the next 30 days. Apache WSS4J before 1.6.17 and 2.x before 2.0.2, as used in Apache CXF 2.7.x before 2.7.13 and 3.0.x before 3.0.2, when using TransportBinding, does not properly enforce the SAML SubjectConfirmation…
CVE-2015-0227, published 2015-02-12. Medium severity, CVSS 5.0. EPSS: 7.5% chance of exploitation in the next 30 days. Apache WSS4J before 1.6.17 and 2.x before 2.0.2 allows remote attackers to bypass the requireSignedEncryptedDataElements configuration via a vectors related to "wrapping attacks."
CVE-2015-0226, published 2017-10-30. High severity, CVSS 7.5. EPSS: 5.5% chance of exploitation in the next 30 days. Apache WSS4J before 1.6.17 and 2.0.x before 2.0.2 improperly leaks information about decryption failures when decrypting an encrypted key or message data, which makes it easier for remote attackers…
CVE-2011-2487, published 2020-03-11. Medium severity, CVSS 5.9. EPSS: 1.8% chance of exploitation in the next 30 days. The implementations of PKCS#1 v1.5 key transport mechanism for XMLEncryption in JBossWS and Apache WSS4J before 1.6.5 is susceptible to a Bleichenbacher attack.
CVE-2026-88920, published 2026-09-30. Critical severity, CVSS 9.8. EPSS: 0.6% chance of exploitation in the next 30 days. An authentication bypass in the DOM security processor in Apache WSS4J allows unauthenticated remote attackers to forge authenticated SOAP messages via a crafted unsigned SAML sender-vouches…
CVE-2026-85532, published 2026-09-30. High severity, CVSS 7.5. EPSS: 0.5% chance of exploitation in the next 30 days. 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…
CVE-2026-92121, published 2026-09-30. High severity, CVSS 7.5. EPSS: 0.5% chance of exploitation in the next 30 days. In the WSS4J streaming (StAX) code, a signature reference using the WS-Security STR-Transform leaves an internal "inside signed content" flag permanently set. The WS-SecurityPolicy enforcer uses that…
CVE-2026-92899, published 2026-09-30. Medium severity, CVSS 4.8. EPSS: 0.5% chance of exploitation in the next 30 days. Apache WSS4J remembers the Nonce of each UsernameToken it accepts, so a captured token cannot be reused. It stored the Nonce as raw base64 text, but authentication decodes that text and uses the…
CVE-2026-95616, published 2026-09-30. High severity, CVSS 7.5. EPSS: 0.4% chance of exploitation in the next 30 days. An integer overflow in WSS4J's DER bounds check lets an oversized allocation pass validation. An unauthenticated attacker can send a SOAP message carrying an X.509 certificate whose…

Latest

CVE-2026-89238, published 2026-09-30. Critical severity, CVSS 9.1. EPSS: 0.3% chance of exploitation in the next 30 days. WSS4J EncryptedHeader child confusion could promote an attacker-controlled plaintext element as the decrypted header, leading to incorrect confidentiality coverage and possible policy bypass. Users…
CVE-2026-87830, published 2026-09-30. Critical severity, CVSS 9.1. EPSS: 0.2% chance of exploitation in the next 30 days. In the StAX streaming WS-SecurityPolicy validator, certain relative or unsupported XPath expressions can be converted into paths that never match the actual XML element path. A remote SOAP peer may…