Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
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
Jul 8, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Sep 18, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
5.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs93th percentile — riskier than 93% 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-2016-9606 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,333 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

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
EcosystemPackageVulnerable rangeFix
Mavenorg.jboss.resteasy:resteasy-bomall versions3.1.2.Finalorg.jboss.resteasy:resteasy-bom:3.1.2.Final

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.jboss.resteasy:resteasy-bom, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. 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.

  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-2016-9606 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2016-9606. 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 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…

ProductFixed inAdvisory
Red Hat JBoss BPMS 6.4see advisoryRHSA-2017:1675
Red Hat JBoss BPMS 7.1see advisoryRHSA-2018:2909
Red Hat JBoss BRMS 6.4see advisoryRHSA-2017:1676
Red Hat JBoss BRMS 7.1see advisoryRHSA-2018:2913
Red Hat JBoss EAP 7see advisoryRHSA-2017:1409
Red Hat JBoss Enterprise Application Platform 6.4see advisoryRHSA-2017:1255
Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 5hibernate4-eap6-0:4.2.26-1.Final_redhat_1.1.ep6.el5RHSA-2017:1256
Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6hibernate4-eap6-0:4.2.26-1.Final_redhat_1.1.ep6.el6RHSA-2017:1254

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2016-9606 in your dependencies?

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

CVE-2016-9606: resteasy-bom RCE (High 8.1) | O3 Security