CVE-2018-1000210

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 1.5%, top 29% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
71.0%
KEV
Not listed

Published

July 13, 2018

Last Modified

November 21, 2024

References (4)

Affected Packages

(2 across 1 ecosystem)
NuGet(2)
PackageVulnerable rangeFixed inDependents
YamlDotNet2.3.0-rc ... 4.3.3-pre0489 (165 versions)5.0.0—
YamlDotNet.Signed3.3.1 ... 4.3.3-pre0489 (155 versions)5.0.0—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 22:12 UTCEG score recompute
  2. 2026-07-22 14:04 UTCEPSS rescore
  3. 2026-07-21 15:21 UTCEPSS rescore
  4. 2026-07-21 09:17 UTCOSV refresh
  5. 2026-07-20 17:04 UTCEPSS rescore
  6. 2026-07-20 17:04 UTCEPSS rescore
  7. 2026-07-19 14:28 UTCEPSS rescore
  8. 2026-07-19 14:28 UTCEPSS rescore
  9. 2026-07-19 02:26 UTCEPSS rescore
  10. 2026-07-19 02:26 UTCEPSS rescore
  11. 2026-07-18 10:01 UTCEPSS rescore
  12. 2026-07-16 16:59 UTCEPSS rescore
  13. 2026-07-16 16:59 UTCEPSS rescore
  14. 2026-07-15 16:55 UTCEPSS rescore
  15. 2026-07-15 16:54 UTCEPSS rescore
  16. 2026-07-15 01:56 UTCEPSS rescore
  17. 2026-07-15 01:56 UTCEPSS rescore
  18. 2026-07-13 22:26 UTCEPSS rescore
  19. 2026-07-13 22:26 UTCEPSS rescore
  20. 2026-07-12 05:43 UTCEPSS rescore
  21. 2026-07-11 08:24 UTCEPSS rescore
  22. 2026-07-09 19:06 UTCEPSS rescore
  23. 2026-07-08 15:11 UTCEPSS rescore
  24. 2026-07-07 13:42 UTCEPSS rescore
  25. 2026-07-06 16:24 UTCEPSS rescore
Show 72 more
  1. 2026-07-06 16:24 UTCEPSS rescore
  2. 2026-07-06 02:20 UTCEPSS rescore
  3. 2026-07-06 02:20 UTCEPSS rescore
  4. 2026-07-05 02:27 UTCEPSS rescore
  5. 2026-07-04 06:28 UTCEPSS rescore
  6. 2026-07-04 06:28 UTCEPSS rescore
  7. 2026-07-04 04:26 UTCOSV refresh
  8. 2026-07-02 16:54 UTCEPSS rescore
  9. 2026-07-01 15:03 UTCEPSS rescore
  10. 2026-06-30 23:19 UTCEPSS rescore
  11. 2026-06-30 23:19 UTCEPSS rescore
  12. 2026-06-29 14:03 UTCEPSS rescore
  13. 2026-06-28 14:04 UTCEPSS rescore
  14. 2026-06-28 04:53 UTCEPSS rescore
  15. 2026-06-28 04:53 UTCEPSS rescore
  16. 2026-06-27 03:06 UTCEPSS rescore
  17. 2026-06-25 13:47 UTCEPSS rescore
  18. 2026-06-24 14:02 UTCEPSS rescore
  19. 2026-06-24 14:02 UTCEPSS rescore
  20. 2026-06-23 21:30 UTCEPSS rescore
  21. 2026-06-23 21:30 UTCEPSS rescore
  22. 2026-06-22 14:23 UTCEPSS rescore
  23. 2026-06-22 14:23 UTCEPSS rescore
  24. 2026-06-21 14:54 UTCEPSS rescore
  25. 2026-06-21 14:54 UTCEPSS rescore
  26. 2026-06-21 01:57 UTCEPSS rescore
  27. 2026-06-21 01:57 UTCEPSS rescore
  28. 2026-06-19 19:23 UTCEPSS rescore
  29. 2026-06-19 19:23 UTCEPSS rescore
  30. 2026-06-18 17:50 UTCEPSS rescore
  31. 2026-06-17 17:50 UTCEPSS rescore
  32. 2026-06-16 17:50 UTCEPSS rescore
  33. 2026-06-15 17:45 UTCEPSS rescore
  34. 2026-06-15 16:13 UTCOSV refresh
  35. 2026-06-14 23:14 UTCEPSS rescore
  36. 2026-06-14 23:14 UTCEPSS rescore
  37. 2026-06-13 22:58 UTCEPSS rescore
  38. 2026-06-13 22:57 UTCEPSS rescore
  39. 2026-06-12 23:09 UTCEPSS rescore
  40. 2026-06-12 23:09 UTCEPSS rescore
  41. 2026-06-11 13:57 UTCEPSS rescore
  42. 2026-06-10 22:15 UTCEPSS rescore
  43. 2026-06-10 13:19 UTCEPSS rescore
  44. 2026-06-08 14:14 UTCEPSS rescore
  45. 2026-06-08 14:14 UTCEPSS rescore
  46. 2026-06-07 15:22 UTCEPSS rescore
  47. 2026-06-07 15:22 UTCEPSS rescore
  48. 2026-06-06 13:45 UTCEPSS rescore
  49. 2026-06-06 13:45 UTCEPSS rescore
  50. 2026-06-05 22:44 UTCEPSS rescore
  51. 2026-06-05 22:44 UTCEPSS rescore
  52. 2026-06-05 06:08 UTCEPSS rescore
  53. 2026-06-05 06:08 UTCEPSS rescore
  54. 2026-06-04 13:10 UTCEPSS rescore
  55. 2026-06-04 13:10 UTCEPSS rescore
  56. 2026-06-02 20:11 UTCEPSS rescore
  57. 2026-06-02 20:11 UTCEPSS rescore
  58. 2026-06-01 13:49 UTCEPSS rescore
  59. 2026-06-01 13:49 UTCEPSS rescore
  60. 2026-05-31 22:28 UTCEPSS rescore
  61. 2026-05-31 00:14 UTCEPSS rescore
  62. 2026-05-31 00:14 UTCEPSS rescore
  63. 2026-05-29 13:41 UTCEPSS rescore
  64. 2026-05-28 13:42 UTCEPSS rescore
  65. 2026-05-28 13:42 UTCEPSS rescore
  66. 2026-05-28 05:16 UTCEG score recompute
  67. 2026-05-27 13:38 UTCEPSS rescore
  68. 2026-05-27 13:38 UTCEPSS rescore
  69. 2026-05-26 13:42 UTCEPSS rescore
  70. 2026-05-26 07:17 UTCEPSS rescore
  71. 2026-05-26 07:17 UTCEPSS rescore
  72. 2026-05-25 16:46 UTCOSV refresh

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2018-1000210?
CVE-2018-1000210 is a high vulnerability published on July 13, 2018. 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…
When was CVE-2018-1000210 disclosed?
CVE-2018-1000210 was first published in the National Vulnerability Database on July 13, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-1000210 actively exploited?
CVE-2018-1000210 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 71.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-1000210?
CVE-2018-1000210 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2018-1000210?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-1000210, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-1000210

Explore →

Is Your Infrastructure Affected by CVE-2018-1000210?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs