CVE-2026-88920

A flaw in the DOM security processor of Apache WSS4J allows unauthenticated remote attackers to perform an authentication bypass . By submitting a crafted, unsigned SAML sender-vouches assertion containing an attacker-controlled key, an attacker can forge authenticated SOAP messages . To mitigate...

CVE-2026-87830

The Apache WSS4J library is vulnerable in its StAX streaming WS-SecurityPolicy validator . The root cause is that certain relative or unsupported XPath expressions can be converted into paths that do not match the actual XML element path. This allows a remote SOAP peer to transmit a required elem...

CVE-2026-89238

The Apache WSS4J library is vulnerable to EncryptedHeader child confusion , which allows an attacker to promote a controlled plaintext element as the decrypted header. This flaw can lead to incorrect confidentiality coverage and a potential policy bypass . To remediate this vulnerability, users s...

CVE-2026-95616

Apache WSS4J is vulnerable to an integer overflow in its DER bounds check, which allows an oversized allocation to bypass validation. An unauthenticated attacker can exploit this by sending a SOAP message containing an X.509 certificate where the SubjectKeyIdentifier extension declares a length o...

CVE-2026-85532

Apache WSS4J is vulnerable to a security issue where it accepts attacker-controlled derived-key lengths and offsets without adequate bounds. This flaw allows for the generation of cryptographically weak keys or may lead to excessive CPU and memory consumption when the software processes crafted W...

CVE-2026-92121

The Apache WSS4J library contains a vulnerability in its streaming (StAX) code . A signature reference utilizing the WS-Security STR-Transform causes an internal "inside signed content" flag to remain permanently set. This leads the WS-SecurityPolicy enforcer to stop evaluating SignedParts and Si...

CVE-2026-92899

The Apache WSS4J library is vulnerable to a replay protection bypass because it stores the Nonce of a UsernameToken as raw base64 text. While authentication uses the decoded bytes, an attacker can re-send a captured request with a space added to the base64 Nonce; the password digest remains valid...