cve.bz

CVE-2018-1000210 yamldotnet project yamldotnet: Deserialization of Untrusted Data

7.8 highEPSS 1.4%Fix available

High (7.8) in yamldotnet project yamldotnet. EPSS 1.4% estimated probability of exploitation activity in the next 30 days. Fixed in YamlDotNet 5.0.0.

On this page
YamlDotNet version 4.3.2 and earlier contains a Insecure Direct Object Reference vulnerability in The default behavior of Deserializer.Deserialize() will deserialize user-controlled types in the line "currentType = Type.GetType(nodeEvent.Tag.Substring(1), throwOnError: false);" and blindly instantiates them. that can result in Code execution in the context of the running process. This attack appear to be exploitable via Victim must parse a specially-crafted YAML file. This vulnerability appears to have been fixed in 5.0.0.

Severity

CVSS 3.0

7.8 high
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
1.4% (unchanged from 1.5% a week ago; 1.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 74th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-502 Deserialization of Untrusted Data
CWE-639 Authorization Bypass Through User-Controlled Key
OWASP Top 10
A01:2025 Broken Access Control, A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

  • YamlDotNet (NuGet): fixed in 5.0.0
  • YamlDotNet.Signed (NuGet): fixed in 5.0.0

Ask an AI about this CVE

Show the promptExplain CVE-2018-1000210 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2018-1000210?via=ask-ai-copy and https://cve.bz/cve/CVE-2018-1000210?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2018-1000210 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
yamldotnet_project:yamldotnetthrough 4.3.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-rpch-cqj9-h65rNuGetYamlDotNet<5.0.05.0.0
GHSA-rpch-cqj9-h65rNuGetYamlDotNet.Signed<5.0.05.0.0

Attack patterns (CAPEC)

  • CAPEC-586 Object Injection Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON