NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

Deserialization of Untrusted Data in org.jboss.resteasy:resteasy-yaml-providerGHSA-m2fv-3rqm-g7p5

HIGHFix: resteasy/resteasy#1555

GHSA-m2fv-3rqm-g7p5 is a high-severity (CVSS 8.1) Improper Input Validation vulnerability in org.jboss.resteasy:resteasy-yaml-provider. A fix is available for org.jboss.resteasy:resteasy-yaml-provider — see the affected versions and patch details below.

Also known asCVE-2018-1051
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs71th percentile — riskier than 71% of all scored CVEsHighest risk
0.19%0.73%1.28%1.82%0.7%1.3%May 26Sep 26Nov 26

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

2 pkgs affected
☕org.jboss.resteasy:resteasy-yaml-provider☕org.jboss.resteasy:resteasy-yaml-provider

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

It was found that the fix for CVE-2016-9606 in versions 3.0.22 and 3.1.2 was incomplete and Yaml unmarshalling in Resteasy is still possible via Yaml.load() in YamlProvider.

Mitigation:

If the YamlProvider is enabled it's recommended to add authentication, and authorization to the endpoint expecting Yaml content to prevent exploitation of this vulnerability.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.jboss.resteasy:resteasy-yaml-providerall versions3.0.26.Finalorg.jboss.resteasy:resteasy-yaml-provider:3.0.26.Final
☕Mavenorg.jboss.resteasy:resteasy-yaml-provider≥ 3.1.0&&< 3.6.0.Final3.6.0.Finalorg.jboss.resteasy:resteasy-yaml-provider:3.6.0.Final

Affected Products

1 product · 2 configurations
Application
resteasyredhat
2 versions
3.0.223.1.2

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

  2. Fix

    Update org.jboss.resteasy:resteasy-yaml-provider to 3.0.26.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m2fv-3rqm-g7p5 is resolved across your whole dependency graph.

  3. Workarounds

    Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

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

This issue only affects applications which have the YamlProvider explicitly enabled by adding or appending a file with the name 'META-INF/services/javax.ws.rs.ext.Providers' to your WAR, or JAR with the contents 'org.jboss.resteasy.plugins.providers.YamlProvider' resteasy-base as shipped in Red Hat Enterprise Linux 7…

Workaround published by Red Hat
If the YamlProvider is enabled it's recommended to add authentication, and authorization to the endpoint expecting Yaml content to prevent exploitation of this vulnerability.
Source: Red Hat security advisory for GHSA-m2fv-3rqm-g7p5 (CC BY 4.0)

Frequently Asked Questions

It was found that the fix for CVE-2016-9606 in versions 3.0.22 and 3.1.2 was incomplete and Yaml unmarshalling in Resteasy is still possible via `Yaml.load()` in YamlProvider. #### Mitigation: If the YamlProvider is enabled it's recommended to add authentication, and authorization to the endpoint expecting Yaml content to prevent exploitation of this vulnerability.
O3 Security · Impact-Aware SCA

Is GHSA-m2fv-3rqm-g7p5 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Deserialization of Untrusted Data in org.jboss.resteasy:rest…