CVE-2018-1051

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.

Published: 2018-01-25 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2018-1051 is rated Moderate Risk (56.5/100): CVSS High severity, with medium exploitation likelihood (EPSS 1.32%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2018-1051

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.73% 1.32% +0.60%
2 2025-03-30 1.40% 0.73% -0.68%
3 2025-03-29 — 1.40% —

Full EPSS history (8 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2018-1051

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.1 3.0 HIGH
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.2 5.9 [email protected]
6.8 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 6.4 [email protected]

Weakness enumeration for CVE-2018-1051

GitHub Security Advisory for CVE-2018-1051

GHSA-m2fv-3rqm-g7p5 · Severity: high · Ecosystem: maven — Deserialization of Untrusted Data in org.jboss.resteasy:resteasy-yaml-provider

OS Trackers for CVE-2018-1051

vendor priority summary link
debian unimportant CVE-2018-1051 unimportant priority: Debian including 2 source packages (resteasy, resteasy3.0), 6 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 6. https://security-tracker.debian.org/tracker/CVE-2018-1051
redhat medium — https://access.redhat.com/security/cve/CVE-2018-1051
ubuntu low CVE-2018-1051 low priority: Ubuntu including 2 source packages (resteasy, resteasy3.0), 38 status rows across 19 suites (artful, bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, trusty, upstream, xenial): not-affected 25, DNE 6, ignored 5, released 2. https://ubuntu.com/security/CVE-2018-1051

Affected software / configurations for CVE-2018-1051

Vendor Product Version Raw CPE
redhat resteasy 3.0.22 cpe:2.3:a:redhat:resteasy:3.0.22:*:*:*:*:*:*:*
redhat resteasy 3.1.2 cpe:2.3:a:redhat:resteasy:3.1.2:*:*:*:*:*:*:*

References for CVE-2018-1051

URL Tags
https://bugzilla.redhat.com/show_bug.cgi?id=1535411 Issue Tracking Vendor Advisory
cvelogic Threat Intelligence