How severe is CVE-2011-2487?

CVE-2011-2487 has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2011-2487?

CVE-2011-2487 affects the following packages: org.apache.ws.security:wss4j (Maven), wss4j:wss4j (Maven). Ecosystems affected: Maven.

How do I fix CVE-2011-2487?

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

How do I detect CVE-2011-2487 in my Maven dependencies?

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.

How do I mitigate CVE-2011-2487 if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against CVE-2011-2487?

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

Is CVE-2011-2487 actively exploited in the wild?

No public exploit code has been indexed for CVE-2011-2487 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2011-2487?

CVE-2011-2487 has an EPSS (Exploit Prediction Scoring System) score of 1.8%, placing it in the 77th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2011-2487 published, and has it been updated?

CVE-2011-2487 was published on April 22, 2022 and was last updated on April 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2011-2487 — wss4j

MEDIUM

CVE-2011-2487 is a medium-severity (CVSS 5.9) 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

Published

Apr 22, 2022

Updated

Apr 16, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Sep 19, 2026 · OSV.dev, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs77th percentile — riskier than 77% 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-2011-2487 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:wss4j☕wss4j:wss4j

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

The implementations of PKCS#1 v1.5 key transport mechanism for XMLEncryption in JBossWS and Apache WSS4J before 1.6.5 is susceptible to a Bleichenbacher attack.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.ws.security:wss4j`	all versions	1.6.5`org.apache.ws.security:wss4j:1.6.5`
☕Maven	`wss4j:wss4j`	all versions	1.6.5`wss4j:wss4j:1.6.5`

Detection & mitigation playbook

Open-source dependency

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.
Fix
Update org.apache.ws.security:wss4j to 1.6.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-2487 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2011-2487 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2011-2487. 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

This flaw affects Apache CXF (WSS4J) and jbossws-native as shipped with various JBoss products. It does not affect JBoss Enterprise Application Platform 6 and JBoss Application Server 7.1.1 and above. These products include WSS4J 1.6.5, which incorporates a fix for this flaw. On affected products, this flaw can be…

Product	Fixed in	Advisory
JBEWP 5 for RHEL 5	`aopalliance-0:1.0-5.2.jdk6.ep5.el5`	RHSA-2013:0196
JBEWP 5 for RHEL 6	`aopalliance-0:1.0-5.3.ep5.el6`	RHSA-2013:0195
JBoss Enterprise BRMS Platform 5.3	see advisory	RHSA-2013:0221
Red Hat JBoss Enterprise Application Platform 5.2	see advisory	RHSA-2013:0194
Red Hat JBoss Enterprise Application Platform 5 for RHEL 5	`aopalliance-0:1.0-5.2.jdk6.ep5.el5`	RHSA-2013:0192
Red Hat JBoss Enterprise Application Platform 5 for RHEL 6	`aopalliance-0:1.0-5.3.ep5.el6`	RHSA-2013:0191
Red Hat JBoss Portal 5.2	see advisory	RHSA-2013:0953
Red Hat JBoss SOA Platform 5.3	see advisory	RHSA-2013:0533

Frequently Asked Questions

The implementations of PKCS#1 v1.5 key transport mechanism for XMLEncryption in JBossWS and Apache WSS4J before 1.6.5 is susceptible to a Bleichenbacher attack.

O3 Security · Impact-Aware SCA

Is CVE-2011-2487 in your dependencies?

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

Scan my dependencies How O3 SCA works