Apache Apache Wss4j

8 CVEs affecting Apache Apache Wss4j. Latest disclosed: 2026-11-16. Critical: 3, High: 3.

Top CVEs affecting Apache Apache Wss4j
CVESeverityScorePublishedSummary
CVE-2026-88920Critical9.82026-09-30An authentication bypass in the DOM security processor in Apache WSS4J allows unauthenticated remote attackers to forge authenticated SOAP messages via a craft…
CVE-2026-89238Critical9.12026-09-30WSS4J EncryptedHeader child confusion could promote an attacker-controlled plaintext element as the decrypted header, leading to incorrect confidentiality cove…
CVE-2026-87830Critical9.12026-09-30In the StAX streaming WS-SecurityPolicy validator, certain relative or unsupported XPath expressions can be converted into paths that never match the actual XM…
CVE-2026-95616High7.52026-09-30An 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…
CVE-2026-92121High7.52026-09-30In the WSS4J streaming (StAX) code, a signature reference using the WS-Security STR-Transform leaves an internal "inside signed content" flag permanently set…
CVE-2026-85532High7.52026-09-30Apache WSS4J accepted attacker-controlled derived-key lengths and offsets without adequate bounds. This could permit cryptographically weak keys or excessive C…
CVE-2026-92899Medium4.82026-09-30Apache 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 authentica…
CVE-2026-1156902026-11-16Apache WSS4J remembers the UsernameToken Nonce, the Timestamp and signature of a signed message, and the ID of a SAML 2.0 "OneTimeUse" assertion, so that a cap…