The YAML Project maintains a foundational serialization library whose deceptively narrow product scope belies its wide embedding across application stacks and infrastructure tools. Its vulnerability profile centers on the inherent risks of parsing and deserializing untrusted data, with recurring exposure in deserialization flaws, uncaught exception handling, and uncontrolled resource consumption that reflect the parsing demands of a format used across configuration management, data exchange, and automation platforms. Live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Yaml Project over time
Signals from CVEs in this vendor scope (4 CVEs).
4 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2023-2251HIGH Uncaught Exception in GitHub repository eemeli/yaml prior to 2.0.0-5. | Apr 24, 2023 | 7.5 | 25 | NO | NO |
CVE-2022-3064HIGH Parsing malicious or large YAML documents can consume excessive amounts of CPU or memory. | Dec 27, 2022 | 7.5 | 25 | NO | NO |
CVE-2021-4235MEDIUM Due to unbounded alias chasing, a maliciously crafted YAML file can cause the system to consume significant system resources. If parsing user input, this may be used as a denial of | Dec 27, 2022 | 5.5 | 20 | NO | NO |
CVE-2022-28948HIGH An issue in the Unmarshal function in Go-Yaml v3 causes the program to crash when attempting to deserialize invalid input. | May 19, 2022 | 7.5 | 20 | NO | NO |
Signals from CVEs in this vendor scope (4 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Yaml Project.
Media articles that mention a CVE ID that affects a product developed by Yaml Project — matched by CVE ID, not by vendor name.