How severe is CVE-2016-3110?

CVE-2016-3110 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2016-3110?

CVE-2016-3110 affects the following packages: org.jboss.mod_cluster:mod_cluster-parent (Maven). Ecosystems affected: Maven.

How do I fix CVE-2016-3110?

Update org.jboss.mod_cluster:mod_cluster-parent to 1.3.3.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-3110 is resolved across your whole dependency graph.

How do I detect CVE-2016-3110 in my Maven dependencies?

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

How do I mitigate CVE-2016-3110 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-2016-3110 actively exploited in the wild?

No public exploit code has been indexed for CVE-2016-3110 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-2016-3110?

CVE-2016-3110 has an EPSS (Exploit Prediction Scoring System) score of 3.6%, placing it in the 90th 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-2016-3110?

CVE-2016-3110 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-2016-3110 published, and has it been updated?

CVE-2016-3110 was published on May 14, 2022 and was last updated on April 14, 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

HIGH severity

CVE-2016-3110 — mod_cluster-parent

HIGH

CVE-2016-3110 is a high-severity (CVSS 7.5) Improper Input Validation vulnerability in org.jboss.mod_cluster:mod_cluster-parent. A fix is available for org.jboss.mod_cluster:mod_cluster-parent — see the affected versions and patch details below.

mod_cluster Denial of Service vulnerability

Published

May 14, 2022

Updated

Apr 14, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

3.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs90th percentile — riskier than 90% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕org.jboss.mod_cluster:mod_cluster-parent

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

mod_cluster, as used in Red Hat JBoss Web Server 2.1, allows remote attackers to cause a denial of service (Apache http server crash) via an MCMP message containing a series of = (equals) characters after a legitimate element.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jboss.mod_cluster:mod_cluster-parent`	all versions	1.3.3.Final`org.jboss.mod_cluster:mod_cluster-parent:1.3.3.Final`

Affected Products

3 products · 7 configurations

fedorafedoraproject

3 versions

282930

Application

jboss enterprise application platformredhat

2 versions

6.0.06.4.0

Application

jboss enterprise web serverredhat

2 versions

2.0.02.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jboss.mod_cluster:mod_cluster-parent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jboss.mod_cluster:mod_cluster-parent to 1.3.3.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-3110 is resolved across your whole dependency graph.
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

Product	Fixed in	Advisory
Red Hat JBoss Enterprise Application Platform 6.4	`mod_cluster`	RHSA-2016:2056
Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6	`hornetq-native-0:2.3.25-4.SP11_redhat_1.ep6.el6`	RHSA-2016:2055
Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 7	`hornetq-native-0:2.3.25-4.SP11_redhat_1.ep6.el7`	RHSA-2016:2054
Red Hat JBoss Enterprise Web Server 2 for RHEL 6	`httpd-0:2.2.26-54.ep6.el6`	RHSA-2016:1649
Red Hat JBoss Enterprise Web Server 2 for RHEL 7	`httpd22-0:2.2.26-56.ep6.el7`	RHSA-2016:1648
Red Hat JBoss Web Server 2.1	see advisory	RHSA-2016:1650

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2016-3110 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works