CVE-2018-1000210: YamlDotNet version 4.3.2 and earlier contains a Insecure Direct Object Reference vulnerability in The default

Q: How do I fix CVE-2018-1000210?

yamldotnet: upgrade to newer than 4.3.2. Exact commands for each OS are on this page.

Q: Is CVE-2018-1000210 being exploited?

CVE-2018-1000210 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2018-1000210 affect?

CVE-2018-1000210 affects yamldotnet. Severity is high (CVSS 7.8). 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.Ta

This month

HIGH 7.8UPGRADE

CVE-2018-1000210 is a high-severity flaw (CVSS 7.8) affecting yamldotnet. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 specia

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.8 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	1.5% (top 26%)
CISA exploited list	No
Weakness	CWE-502, CWE-639
Published	2018-07-13
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: yamldotnet project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-07-13 18:29 UTCPublished CVE record published
2026-06-17 01:32 UTCUpdated Record last modified

yamldotnet project yamldotnet UPGRADE

Affected: <= 4.3.2

Fixed in: newer than 4.3.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy yamldotnet || rpm -q yamldotnet || yamldotnet --version

2. UPGRADE to newer than 4.3.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade yamldotnet

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade yamldotnet

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-1000210?

yamldotnet: upgrade to newer than 4.3.2. Exact commands for each OS are on this page.

Is CVE-2018-1000210 being exploited?

CVE-2018-1000210 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-1000210 affect?

CVE-2018-1000210 affects yamldotnet. Severity is high (CVSS 7.8). 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.Ta

How urgent is CVE-2018-1000210?

Priority 46/100. High severity

References

← Back to latest CVEs