Quick answers
- Is CVE-2026-95616 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-95616 being exploited in the wild.
- How severe is CVE-2026-95616?
- High severity, with a CVSS score of 7.5, published 30 September 2026.
- Which products and versions are affected?
- Apache WSS4J Before 2.4.4, 3.0.x before 3.0.6, 4.0.x before 4.0.2.
- Is there a fix for CVE-2026-95616?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-95616 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-95616?
- Check whether you run Apache WSS4J at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An integer overflow in WSS4J's DER bounds check allows validation of oversized extension length declarations. An unauthenticated attacker sends a SOAP message with an X.509 certificate whose SubjectKeyIdentifier extension declares a length of 0x7FFFFFFF; the library decodes this during signature key reference resolution before message authentication, causing an eleven-byte extension to trigger a 2 GB memory allocation. Repeated requests exhaust server memory, resulting in denial of service.
Affected products
- Apache WSS4J Before 2.4.4, 3.0.x before 3.0.6, 4.0.x before 4.0.2
Timeline
- 2026-09-30: disclosed