Skip to main content
VulnerabilityPublished

CVE-2026-95616: Apache WSS4J · Integer Overflow

Affects Apache WSS4JSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High · fixed in 4.0.2 : patch Apache WSS4J soon.

Data as of 14 Nov 2026, 20:44 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.0.2, 3.0.6, 2.4.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 14 Nov 2026.

What to do

Upgrade Apache to 4.0.2, 3.0.6 or 2.4.4.

Affected software

ProductAffectedFixed in
Apache Software FoundationApache WSS4JAffected
  • >=4.0.0 <4.0.2
Fixed in
  • 4.0.2
Apache Software FoundationApache WSS4JAffected
  • >=3.0.0 <3.0.6
Fixed in
  • 3.0.6
Apache Software FoundationApache WSS4JAffected
  • <2.4.4
Fixed in
  • 2.4.4
MavenApache Software Foundation/org.apache.wss4j:wss4j-ws-security-commonpkg:maven/Apache Software Foundation/org.apache.wss4j:wss4j-ws-security-commonOther threatsAffected
  • >=4.0.0 <4.0.2
  • >=3.0.0 <3.0.6
  • <2.4.4
Fixed in
  • 4.0.2
  • 3.0.6
  • 2.4.4

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 Apache WSS4J to versions 4.0.2, 3.0.6, or 2.4.4, which contain fixes for this vulnerability. No other mitigation is indicated or required as the issue is resolved in these official releases.

Description

An 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.509 certificate whose SubjectKeyIdentifier extension declares a length of 0x7FFFFFFF; WSS4J decodes this while resolving the signature's key reference, before the message is authenticated, so an eleven-byte extension triggers a 2 GB allocation. Repeated requests exhaust server memory. Users are recommended to upgrade to versions 4.0.2 or 3.0.6 or 2.4.4, which fix this issue.

References

Community reviews

Loading reviews…