CVE-2026-92121VulnerabilityPublished 30 Sep 2026Updated 4 Nov 2026

In the WSS4J streaming (StAX) code, a signature reference using the WS-Security STR-Transform leaves an internal

Affects wss4jSource GCVE Database

Compare

Authoritative record:CVE-2026-92121· High 7.5

Not known to be exploited · CVSS 7.5 High.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.10wss4j`pkg:deb/ubuntu/wss4j?arch=source&distro=stonking`Other threats	Affected =1.6.19-4build1	Fixed in–
Ubuntu 22.04 LTSwss4j`pkg:deb/ubuntu/wss4j?arch=source&distro=jammy`Other threats	Affected =1.6.19-2	Fixed in–
Ubuntu 20.04 LTSwss4j`pkg:deb/ubuntu/wss4j?arch=source&distro=focal`Other threats	Affected =1.6.19-2	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade to WSS4J versions 4.0.2, 3.0.6, or 2.4.4, which contain fixes for this vulnerability. No other mitigations are indicated as signature verification remains unaffected and the DOM code is not vulnerable.

Description

A vulnerability in the WSS4J streaming (StAX) code causes an internal flag related to signed content to remain set incorrectly when using the WS-Security STR-Transform. This leads the WS-SecurityPolicy enforcer to incorrectly assume that the SOAP Body is signed, even when it is not, bypassing protection against XML Signature Wrapping attacks. Signature verification itself is not affected, and the DOM code is not vulnerable. Fixed versions 4.0.2, 3.0.6, and 2.4.4 address this issue.

Impact

This vulnerability allows an attacker to bypass WS-Security policy enforcement that requires the SOAP Body to be signed, potentially enabling XML Signature Wrapping attacks. Although the signature verification process itself is not compromised, the policy enforcer's incorrect flag state means unsigned SOAP Body content may be accepted as valid, undermining message integrity assurances. This can lead to unauthorized message modifications being accepted by the application.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2026, 21:16 UTC

Technical details

References

Community reviews

Related threats