Security advisory
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2018-1000210
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 31 Oct 2026, 09:59 UTC · Revision 1
Source evidence
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.
osv:CVE-2018-1000210
Complete source record
{
"id": "eb9e85c3f1ec802123deefaf80200a27a9efe3d6578ed3db2eca47f17a1197a3",
"url": "https://osv.dev/vulnerability/CVE-2018-1000210",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "CVE-2018-1000210",
"summary": "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.",
"evidence": "osv:CVE-2018-1000210",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2018-1000210",
"aliases": [
"CVE-2018-1000210",
"GHSA-rpch-cqj9-h65r"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/aaubry/yamldotnet",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"last_affected": "8f20a18bb8a8c026bef7ce5ad66e7d8e198426df"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:yamldotnet_project:yamldotnet:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0"
},
{
"last_affected": "4.3.2"
}
],
"source": "CPE_RANGE"
}
]
}
}
],
"versions": [
"v4.3.2",
"v4.3.1",
"v4.3.0",
"v4.2.4",
"v4.2.3",
"v4.2.2",
"v4.2.1",
"v4.2.0",
"v4.1.0",
"v4.0.0",
"v3.9.0",
"v3.8.0",
"v3.7.0",
"v3.6.1",
"v3.6.0",
"v3.3.1",
"v3.3.0",
"v3.2.2",
"v3.2.1",
"v3.2.0",
"v3.1.1",
"v3.1.0",
"v3.0.0",
"v2.3.0-rc",
"v2.2.0",
"v2.1.0",
"v2.0.1",
"v2.0.0",
"v1.3.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2018-1000210.json"
}
}
],
"modified": "2026-10-20T10:49:38.558344124Z",
"provider": "osv",
"references": [
"https://github.com/aaubry/YamlDotNet#version-500",
"https://github.com/aaubry/YamlDotNet/blob/f96b7cc40a0498f8bafdeb49df3aa23aa2c60993/YamlDotNet/Serialization/NodeTypeResolvers/TypeNameInTagNodeTypeResolver.cs#L35"
],
"provider_metadata": {}
},
"related_cves": [
{
"value": "CVE-2018-1000210",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 380628,
"published_at": "2018-07-13T18:29:00.397+00:00"
}