Snakeyamlproject Snakeyaml
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in Snakeyamlproject Snakeyaml.
By the Year
In 2026 there have been 0 vulnerabilities in Snakeyamlproject Snakeyaml. Snakeyaml did not have any published security vulnerabilities last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 0 | 0.00 |
| 2025 | 0 | 0.00 |
| 2024 | 0 | 0.00 |
| 2023 | 0 | 0.00 |
| 2022 | 7 | 6.97 |
| 2021 | 0 | 0.00 |
| 2020 | 0 | 0.00 |
| 2019 | 1 | 0.00 |
It may take a day or so for new Snakeyaml vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Snakeyamlproject Snakeyaml Security Vulnerabilities
SnakeYaml Constructor Type Bypass RCE via Unsafe Deserialization Fixed in 2.0
CVE-2022-1471
9.8 - Critical
- December 01, 2022
SnakeYaml's Constructor() class does not restrict types which can be instantiated during deserialization. Deserializing yaml content provided by an attacker can lead to remote code execution. We recommend using SnakeYaml's SafeConsturctor when parsing untrusted content to restrict deserialization. We recommend upgrading to version 2.0 and beyond.
Marshaling, Unmarshaling
SnakeYAML Denial of Service via Stack Overflow in YAML Parsing
CVE-2022-41854
6.5 - Medium
- November 11, 2022
Those using Snakeyaml to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stack overflow. This effect may support a denial of service attack.
Memory Corruption
SnakeYAML DOS via Untrusted YAML Stack-Overflow
CVE-2022-38752
6.5 - Medium
- September 05, 2022
Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stack-overflow.
Memory Corruption
SnakeYAML YAML DOS via StackOverflow
CVE-2022-38751
6.5 - Medium
- September 05, 2022
Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow.
Memory Corruption
Java: SnakeYAML Untrusted YAML Parsing DOS via StackOverflow
CVE-2022-38749
6.5 - Medium
- September 05, 2022
Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow.
Memory Corruption
SnakeYAML DOS via StackOverflow when parsing untrusted YAML
CVE-2022-38750
5.5 - Medium
- September 05, 2022
Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow.
Memory Corruption
org.yaml:snakeyaml DoS: missing nested depth limit (v<1.31)
CVE-2022-25857
7.5 - High
- August 30, 2022
The package org.yaml:snakeyaml from 0 and before 1.31 are vulnerable to Denial of Service (DoS) due missing to nested depth limitation for collections.
XEE
The Alias feature in SnakeYAML before 1.26
CVE-2017-18640
- December 12, 2019
The Alias feature in SnakeYAML before 1.26 allows entity expansion during a load operation, a related issue to CVE-2003-1564.
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Snakeyamlproject Snakeyaml or by Snakeyamlproject? Click the Watch button to subscribe.
