How severe is CVE-2026-92121?

CVE-2026-92121 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.

Is CVE-2026-92121 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (26th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-92121?

CVE-2026-92121 affects Apache Wss4j. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-92121?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2026-92121 published?

CVE-2026-92121 was published on 2026-09-30 and last updated on 2026-10-06.

CVE-2026-92121

CVE-2026-92121 is a high-severity vulnerability in Apache Wss4j with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-693.

Key facts

Severity: High (CVSS 3.x base score 7.5)
EPSS exploit prediction: 0% (26th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-693
Affected product: Apache Wss4j
Published: 2026-09-30
Last modified: 2026-10-06

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.

Frequently asked questions

What is CVE-2026-92121?: 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.
How severe is CVE-2026-92121?: CVE-2026-92121 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.
Is CVE-2026-92121 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (26th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-92121?: CVE-2026-92121 affects Apache Wss4j. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-92121?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-92121 published?: CVE-2026-92121 was published on 2026-09-30 and last updated on 2026-10-06.

References

Affected products (1)

cpe:2.3:a:apache:wss4j:*:*:*:*:*:*:*:*

More vulnerabilities in Apache Wss4j

CVE-2026-88920 — Critical (CVSS 9.8): An authentication bypass in the DOM security processor in Apache WSS4J allows unauthenticated remote attackers to forge…
CVE-2026-89238 — Critical (CVSS 9.1): WSS4J EncryptedHeader child confusion could promote an attacker-controlled plaintext element as the decrypted header,…
CVE-2026-87830 — Critical (CVSS 9.1): In the StAX streaming WS-SecurityPolicy validator, certain relative or unsupported XPath expressions can be converted…
CVE-2020-13936 — High (CVSS 8.8): An attacker that is able to modify Velocity templates may execute arbitrary Java code or run arbitrary system commands…
CVE-2026-95616 — High (CVSS 7.5): An integer overflow in WSS4J's DER bounds check lets an oversized allocation pass validation. An unauthenticated…
CVE-2026-85532 — High (CVSS 7.5): Apache WSS4J accepted attacker-controlled derived-key lengths and offsets without adequate bounds. This could permit…

All CVEs affecting Apache Wss4j →

Other CWE-693 (Protection Mechanism Failure) vulnerabilities

CVE-2026-93606 — Critical (CVSS 10.0): vm2 (npm) versions 3.12.0 and earlier contain a sandbox escape in `VM` and `NodeVM`. When an embedder exposes a host…
CVE-2026-93605 — Critical (CVSS 10.0): vm2 NodeVM versions before 3.12.1 contain a sandbox escape vulnerability where the DANGEROUS_BUILTINS denylist omits…
CVE-2026-92956 — Critical (CVSS 10.0): vm2 versions 3.10.1 through 3.11.6 contain a sandbox escape reachable from a default `new VM()` sandbox when running on…
CVE-2026-75874 — Critical (CVSS 10.0): Sandbox escape in the Remote Settings Client component. This vulnerability was fixed in Firefox 154, Thunderbird 154,…
CVE-2026-47140 — Critical (CVSS 10.0): vm2 is an open source vm/sandbox for Node.js. Prior to version 3.11.4, NodeVM blocks several dangerous Node.js builtins…
CVE-2026-34208 — Critical (CVSS 10.0): SandboxJS is a JavaScript sandboxing library. Prior to 0.8.36, SandboxJS blocks direct assignment to global objects…

Browse all CWE-693 (Protection Mechanism Failure) vulnerabilities →