How severe is CVE-2016-9606?

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

Which packages are affected by CVE-2016-9606?

CVE-2016-9606 affects the following packages: org.jboss.resteasy:resteasy-bom (Maven). Ecosystems affected: Maven.

How do I fix CVE-2016-9606?

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

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

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

How do I mitigate CVE-2016-9606 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.

Is CVE-2016-9606 actively exploited in the wild?

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

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

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

CVE-2016-9606 was published on March 9, 2018 and was last updated on October 24, 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

HIGH severity

CVE-2016-9606 — resteasy-bom

HIGH

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

JBoss RESTEasy vulnerable to Improper Input Validation

Also known asGHSA-hgjr-xwj3-jfvw

Published

Mar 9, 2018

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

6.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs93th percentile — riskier than 93% 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.resteasy:resteasy-bom

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

JBoss RESTEasy before version 3.1.2 could be forced into parsing a request with YamlProvider, resulting in unmarshalling of potentially untrusted data which could allow an attacker to execute arbitrary code with RESTEasy application permissions.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jboss.resteasy:resteasy-bom`	all versions	3.1.2.Final`org.jboss.resteasy:resteasy-bom:3.1.2.Final`

Affected Products

1 product · 1 configurations

Application

resteasyredhat

≤ 3.1.1

range

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.resteasy:resteasy-bom, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jboss.resteasy:resteasy-bom to 3.1.2.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-9606 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.

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

YamlProvider was removed the default list of providers to prevent a malicous user from requesting a payload be marshalled with Yaml. If marshalling of Yaml content is desired, add, or append a file with the name 'META-INF/services/javax.ws.rs.ext.Providers' to your WAR, or JAR with the contents…

Workaround published by Red Hat

Add authentication and authorization to any Resteasy endpoint which doesn't define a mime type, or defines a multipart mime type.

Source: Red Hat security advisory for CVE-2016-9606 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat JBoss BPMS 6.4	see advisory	RHSA-2017:1675
Red Hat JBoss BPMS 7.1	see advisory	RHSA-2018:2909
Red Hat JBoss BRMS 6.4	see advisory	RHSA-2017:1676
Red Hat JBoss BRMS 7.1	see advisory	RHSA-2018:2913
Red Hat JBoss EAP 7.0	see advisory	RHSA-2017:1409
Red Hat JBoss Enterprise Application Platform 6.4	see advisory	RHSA-2017:1255
Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 5	`hibernate4-eap6-0:4.2.26-1.Final_redhat_1.1.ep6.el5`	RHSA-2017:1256
Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6	`hibernate4-eap6-0:4.2.26-1.Final_redhat_1.1.ep6.el6`	RHSA-2017:1254

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2016-9606 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works