CVE-2026-92121 Apache WSS4J: WS-SecurityPolicy signature checks skipped in the streaming code after an STR-Transform reference
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- No known exploitation · automatable: yes · technical impact: partial
- Technology
- UbuntuDebianRed Hat
Description
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 flag to decide whether an element needs checking, so it stops evaluating SignedParts and SignedElements for the rest of the message. A policy requiring the SOAP Body to be signed is then satisfied even when the Body carries no signature, removing the protection against XML Signature Wrapping. Signature verification itself is unaffected. The DOM code is not affected.
Users are recommended to upgrade to versions 4.0.2 or 3.0.6 or 2.4.4 which fix this issue.
Upgrade path
15 packages: 2 fixed, 13 with no fix yet.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| debian/wss4j(Debian 13) | = 1.6.19-4; All versions | No fix listed | No fix yet |
| debian/wss4j(Debian 14) | = 1.6.19-4; All versions | No fix listed | No fix yet |
| redhat/wss4j(Red Hat camel_spring_boot 4) | All versions | No fix listed | No fix yet |
| redhat/wss4j-ws-security-policy-stax(Red Hat camel_quarkus 3) | All versions | No fix listed | No fix yet |
| redhat/wss4j-ws-security-policy-stax(Red Hat camel_spring_boot 4) | All versions | No fix listed | No fix yet |
| redhat/wss4j-ws-security-policy-stax(Red Hat jboss_enterprise_application_platform 8) | All versions | No fix listed | No fix yet |
| redhat/wss4j-ws-security-policy-stax(Red Hat jbosseapxp) | All versions | No fix listed | No fix yet |
| redhat/wss4j-ws-security-stax(Red Hat camel_quarkus 3) | All versions | No fix listed | No fix yet |
| redhat/wss4j-ws-security-stax(Red Hat camel_spring_boot 4) | All versions | No fix listed | No fix yet |
| redhat/wss4j-ws-security-stax(Red Hat jboss_enterprise_application_platform 8) | All versions | No fix listed | No fix yet |
| redhat/wss4j-ws-security-stax(Red Hat jbosseapxp) | All versions | No fix listed | No fix yet |
| ubuntu/wss4j(Ubuntu 22.04) | All versions | No fix listed | No fix yet |
| ubuntu/wss4j(Ubuntu 26.10) | All versions | No fix listed | No fix yet |
| apache wss4j | < 2.4.4; >= 3.0.0, < 3.0.6; >= 4.0.0, < 4.0.2 | 2.4.4, 3.0.6, 4.0.2 | Fixed |
| org.apache.wss4j/wss4j-ws-security-stax(Maven) | < 2.4.4; >= 3.0.0, < 3.0.6; >= 4.0.0, < 4.0.2 | 2.4.4, 3.0.6, 4.0.2 | Fixed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| org.apache.wss4j/wss4j-ws-security-stax(Maven) | >= 4.0.0, < 4.0.2 | 4.0.2 |
| org.apache.wss4j/wss4j-ws-security-stax(Maven) | >= 3.0.0, < 3.0.6 | 3.0.6 |
| org.apache.wss4j/wss4j-ws-security-stax(Maven) | < 2.4.4 | 2.4.4 |
| redhat/wss4j-ws-security-policy-stax(Red Hat:camel_quarkus:3) | All versions | No fix listed |
| redhat/wss4j-ws-security-stax(Red Hat:camel_quarkus:3) | All versions | No fix listed |
| redhat/wss4j(Red Hat:camel_spring_boot:4) | All versions | No fix listed |
| redhat/wss4j-ws-security-policy-stax(Red Hat:camel_spring_boot:4) | All versions | No fix listed |
| redhat/wss4j-ws-security-stax(Red Hat:camel_spring_boot:4) | All versions | No fix listed |
| redhat/wss4j(Red Hat:jboss_fuse:7) | All versions | No fix listed |
| redhat/wss4j-ws-security-policy-stax(Red Hat:jboss_fuse:7) | All versions | No fix listed |
| redhat/wss4j-ws-security-stax(Red Hat:jboss_fuse:7) | All versions | No fix listed |
| redhat/jboss-eap-7/eap74-els-openjdk11-openshift-rhel8(Red Hat:jboss_enterprise_application_platform:7) | All versions | No fix listed |
| redhat/jboss-eap-7/eap74-els-openjdk17-openshift-rhel8(Red Hat:jboss_enterprise_application_platform:7) | All versions | No fix listed |
| redhat/jboss-eap-7/eap74-els-openjdk8-openshift-rhel8(Red Hat:jboss_enterprise_application_platform:7) | All versions | No fix listed |
| redhat/wss4j(Red Hat:jboss_enterprise_application_platform:7) | All versions | No fix listed |
| redhat/wss4j-ws-security-policy-stax(Red Hat:jboss_enterprise_application_platform:7) | All versions | No fix listed |
| redhat/wss4j-ws-security-stax(Red Hat:jboss_enterprise_application_platform:7) | All versions | No fix listed |
| redhat/wss4j-ws-security-policy-stax(Red Hat:jboss_enterprise_application_platform:8) | All versions | No fix listed |
| redhat/wss4j-ws-security-stax(Red Hat:jboss_enterprise_application_platform:8) | All versions | No fix listed |
| redhat/wss4j-ws-security-policy-stax(Red Hat:jbosseapxp) | All versions | No fix listed |
| redhat/wss4j-ws-security-stax(Red Hat:jbosseapxp) | All versions | No fix listed |
| redhat/wss4j-ws-security-policy-stax(Red Hat:red_hat_single_sign_on:7) | All versions | No fix listed |
| redhat/wss4j-ws-security-stax(Red Hat:red_hat_single_sign_on:7) | All versions | No fix listed |
| debian/wss4j(Debian:13) | All versions | No fix listed |
| debian/wss4j(Debian:13) | = 1.6.19-4 | No fix listed |
Show 7 more
| Product | Affected versions | Fixed in |
|---|---|---|
| debian/wss4j(Debian:14) | All versions | No fix listed |
| debian/wss4j(Debian:14) | = 1.6.19-4 | No fix listed |
| ubuntu/wss4j(Ubuntu:22.04) | All versions | No fix listed |
| ubuntu/wss4j(Ubuntu:26.10) | All versions | No fix listed |
| apache wss4j | < 2.4.4 | 2.4.4 |
| apache wss4j | >= 3.0.0, < 3.0.6 | 3.0.6 |
| apache wss4j | >= 4.0.0, < 4.0.2 | 4.0.2 |
References
- lists.apache.org vendor-advisory
- www.openwall.com mailing-list third-party-advisory
- Red Hat CVE page vendor-advisory
- Red Hat Bugzilla 2543905 issue-tracking
- www.cve.org
- nvd.nist.gov
- Debian Security Tracker CVE-2026-92121 vendor-advisory
- Ubuntu CVE tracker vendor-advisory
- bugs.debian.org issue-tracking
- ENISA EUVD EUVD-2026-89795 third-party-advisory