How severe is CVE-2026-95616?

CVE-2026-95616 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 none, and availability high.

Is CVE-2026-95616 being actively exploited?

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

What products are affected by CVE-2026-95616?

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

How do I fix CVE-2026-95616?

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-95616 published?

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

CVE-2026-95616

CVE-2026-95616 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-190.

Key facts

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

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.

Frequently asked questions

What is CVE-2026-95616?: 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.
How severe is CVE-2026-95616?: CVE-2026-95616 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 none, and availability high.
Is CVE-2026-95616 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (20th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-95616?: CVE-2026-95616 affects Apache Wss4j. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-95616?: 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-95616 published?: CVE-2026-95616 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-92121 — High (CVSS 7.5): In the WSS4J streaming (StAX) code, a signature reference using the WS-Security STR-Transform leaves an internal…
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-190 (Integer Overflow or Wraparound) vulnerabilities

CVE-2026-4689 — Critical (CVSS 10.0): Sandbox escape due to incorrect boundary conditions, integer overflow in the XPCOM component. This vulnerability was…
CVE-2026-24814 — Critical (CVSS 10.0): Integer Overflow or Wraparound vulnerability in swoole swoole-src (thirdparty/hiredis modules). This vulnerability is…
CVE-2025-64721 — Critical (CVSS 10.0): Sandboxie is a sandbox-based isolation software for 32-bit and 64-bit Windows NT-based operating systems. In versions…
CVE-2015-5108 — Critical (CVSS 10.0): Integer overflow in Adobe Reader and Acrobat 10.x before 10.1.15 and 11.x before 11.0.12, Acrobat and Acrobat Reader DC…
CVE-2015-5097 — Critical (CVSS 10.0): Integer overflow in Adobe Reader and Acrobat 10.x before 10.1.15 and 11.x before 11.0.12, Acrobat and Acrobat Reader DC…
CVE-2013-2555 — Critical (CVSS 10.0): Integer overflow in Adobe Flash Player before 10.3.183.75 and 11.x before 11.7.700.169 on Windows and Mac OS X, before…

Browse all CWE-190 (Integer Overflow or Wraparound) vulnerabilities →