Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven
Not in CISA KEV
HIGH severity

CVE-2015-0226 wss4j

HIGH

CVE-2015-0226 is a high-severity (CVSS 7.5) Broken Cryptographic Algorithm vulnerability in org.apache.ws.security:wss4j. A fix is available for org.apache.ws.security:wss4j — see the affected versions and patch details below.

Use of a Broken or Risky Cryptographic Algorithm in Apache WSS4J

Also known asGHSA-vjwc-5hfh-2vv5
Published
Oct 30, 2017
Updated
Apr 10, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Sep 18, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
5.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs92th percentile — riskier than 92% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2015-0226 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

2 pkgs affected
org.apache.ws.security:wss4jorg.apache.wss4j:wss4j-ws-security-dom

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Apache WSS4J before 1.6.17 and 2.0.x before 2.0.2 improperly leaks information about decryption failures when decrypting an encrypted key or message data, which makes it easier for remote attackers to recover the plaintext form of a symmetric key via a series of crafted messages. NOTE: this vulnerability exists because of an incomplete fix for CVE-2011-2487.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.apache.ws.security:wss4jall versions1.6.17org.apache.ws.security:wss4j:1.6.17
Mavenorg.apache.wss4j:wss4j-ws-security-dom2.0.0&&< 2.0.22.0.2org.apache.wss4j:wss4j-ws-security-dom:2.0.2

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.ws.security:wss4j, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.apache.ws.security:wss4j to 1.6.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-0226 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2015-0226 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2015-0226. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant
ProductFixed inAdvisory
Red Hat JBoss A-MQ 6.2see advisoryRHSA-2015:1177
Red Hat JBoss Data Grid 6.4wss4jRHSA-2015:0773
Red Hat JBoss Enterprise Application Platform 6.4see advisoryRHSA-2015:0849
Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 5apache-commons-cli-eap6-0:1.2.0-1.redhat_8.1.ep6.el5RHSA-2015:0846
Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6apache-commons-cli-eap6-0:1.2.0-1.redhat_8.1.ep6.el6RHSA-2015:0847
Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 7apache-commons-daemon-eap6-1:1.0.15-8.redhat_1.ep6.el7RHSA-2015:0848
Red Hat JBoss Fuse 6.2see advisoryRHSA-2015:1176
Red Hat JBoss Portal 6.2see advisoryRHSA-2015:1009

Frequently Asked Questions

Apache WSS4J before 1.6.17 and 2.0.x before 2.0.2 improperly leaks information about decryption failures when decrypting an encrypted key or message data, which makes it easier for remote attackers to recover the plaintext form of a symmetric key via a series of crafted messages. NOTE: this vulnerability exists because of an incomplete fix for CVE-2011-2487.
O3 Security · Impact-Aware SCA

Is CVE-2015-0226 in your dependencies?

O3 Security finds CVE-2015-0226 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2015-0226: wss4j (High 7.5) | O3 Security