How severe is CVE-2014-0086?

No CVSS score has been assigned to CVE-2014-0086 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2014-0086?

CVE-2014-0086 affects the following packages: org.richfaces:richfaces (Maven), org.richfaces:richfaces (Maven). Ecosystems affected: Maven.

How do I fix CVE-2014-0086?

A fix is available for CVE-2014-0086; check the affected-versions list above or the advisory for the patched release of org.richfaces:richfaces, then make sure no transitive dependency still pins the vulnerable range.

How do I detect CVE-2014-0086 in my Maven dependencies?

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

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

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2014-0086 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2014-0086, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2014-0086?

CVE-2014-0086 has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 73th 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.

What type of vulnerability is CVE-2014-0086?

CVE-2014-0086 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2014-0086 published, and has it been updated?

CVE-2014-0086 was published on May 17, 2022 and was last updated on April 13, 2025. 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

CVE-2014-0086 — richfaces

Fix: pslegr/core-1@8131f15

CVE-2014-0086 is a Improper Input Validation vulnerability in org.richfaces:richfaces. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.richfaces:richfaces — see the affected versions and patch details below.

JBoss RichFaces Improper Input Validation vulnerability

Published

May 17, 2022

Updated

Apr 13, 2025

Affected

2 pkgs

Patched

1 / 2

Exploits

1 known

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs73th percentile — riskier than 73% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

☕org.richfaces:richfaces☕org.richfaces:richfaces

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 doFilter function in webapp/PushHandlerFilter.java in JBoss RichFaces 4.3.4, 4.3.5, and 5.x allows remote attackers to cause a denial of service (memory consumption and out-of-memory error) via a large number of malformed atmosphere push requests.

Affected Packages

2 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.richfaces:richfaces`	≥ 4.3.4	No fix
☕Maven	`org.richfaces:richfaces`	≥ 5.0.0.Alpha1&&< 5.0.0.Alpha3	5.0.0.Alpha3`org.richfaces:richfaces:5.0.0.Alpha3`

Affected Products

2 products · 6 configurations

Application

jboss web framework kitredhat

1 version

2.5.0

Application

richfacesredhat

3 versions

4.3.44.3.55.0.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The doFilter function in webapp/PushHandlerFilter.java in JBoss RichFace…

github.comNVDDec 2017

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.richfaces:richfaces, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
A fix is available for CVE-2014-0086; check the affected-versions list above or the advisory for the patched release of org.richfaces:richfaces, then make sure no transitive dependency still pins the vulnerable range.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

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 HatModerate

RHSA-2015:1009Red Hat JBoss Portal 6.2 RHSA-2014:0335Red Hat JBoss Web Framework Kit 2.5

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-0086 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works