VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.yaml:snakeyaml: vulnerability history, versions and safety

org.yaml:snakeyaml is a package in the Maven ecosystem. Vulert records 9 vulnerabilities for it across 30 releases, from Jun 2021 to Dec 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
9 vulnerabilities recorded H3 M6
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all org.yaml:snakeyaml vulnerabilities

Vulert verdict on org.yaml:snakeyaml 2.7 i

Updated on 23 Oct 2026

Good news: 2.7, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 9.

Package health score 76/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Inactive

What to do: Stay on 2.7 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.7 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.7 — unaffected i
  • Vulnerabilities on record 9 over 1 year · 0 in the last year i
  • Latest disclosure 12 Dec 2022 i
  • Highest CVSS 8.3 i
  • With no published fix 0 i
  • Depended on by 2,284 packages i
  • Last release 1 month ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by Maven Central, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for org.yaml:snakeyaml, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.7 30 Aug 2026 none Apache-2.0 — Details →
2.6 26 Feb 2026 none Apache-2.0 — Details →
2.5 31 Aug 2025 none Apache-2.0 — Details →
2.4 15 Feb 2025 none Apache-2.0 — Details →
2.3 31 Aug 2024 none Apache-2.0 — Details →
2.2 27 Aug 2023 none Apache-2.0 — Details →
2.1 04 Aug 2023 none Apache-2.0 — Details →
2.0 26 Feb 2023 none Apache-2.0 — Details →
1.33 26 Sep 2022 H1 Apache-2.0 Yes Details →
1.32 12 Sep 2022 H1 Apache-2.0 Yes Details →
1.31 27 Aug 2022 H1 M2 Apache-2.0 Yes Details →
1.30 14 Dec 2021 H2 M6 Apache-2.0 Yes Details →
1.29 08 Jun 2021 H2 M6 Apache-2.0 Yes Details →
1.28 22 Feb 2021 H2 M6 Apache-2.0 Yes Details →
1.27 11 Sep 2020 H2 M6 Apache-2.0 Yes Details →
1.26 28 Feb 2020 H2 M6 Apache-2.0 Yes Details →
1.25 13 Aug 2019 H3 M6 Apache-2.0 Yes Details →
1.24 28 Feb 2019 H3 M6 Apache-2.0 Yes Details →
1.23 27 Aug 2018 H3 M6 Apache-2.0 Yes Details →
1.22 25 Aug 2018 H3 M6 Apache-2.0 Yes Details →
1.21 13 Apr 2018 H3 M6 Apache-2.0 Yes Details →
1.20 28 Feb 2018 H3 M6 Apache-2.0 Yes Details →
1.19 14 Oct 2017 H3 M6 Apache-2.0 Yes Details →
1.18 22 Feb 2017 H3 M6 Apache-2.0 Yes Details →
1.17 19 Feb 2016 H3 M6 Apache-2.0 Yes Details →
1.16 18 Aug 2015 H3 M6 Apache-2.0 Yes Details →
1.15 19 Feb 2015 H3 M6 Apache-2.0 Yes Details →
1.14 29 Aug 2014 H3 M6 Apache-2.0 Yes Details →
1.13 05 Sep 2013 H3 M6 Apache-2.0 Yes Details →
1.12 02 Mar 2013 H3 M6 Apache-2.0 Yes Details →
1.11 30 Sep 2012 H3 M6 Apache-2.0 Yes Details →
1.10 13 Feb 2012 H3 M6 Apache-2.0 Yes Details →
1.9 15 Aug 2011 H3 M6 Apache-2.0 Yes Details →
1.8 15 Feb 2011 H3 M6 Apache-2.0 Yes Details →
1.7 12 Aug 2010 H3 M6 Apache-2.0 Yes Details →
1.6 08 Mar 2010 H3 M6 Apache-2.0 Yes Details →
1.5 08 Mar 2010 H3 M6 Apache-2.0 Yes Details →
1.4 26 Aug 2009 H3 M6 Apache-2.0 Yes Details →

All 38 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2022 8

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 9 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for org.yaml:snakeyaml

The 5 most severe of 9 vulnerabilities recorded for this package

Search all 9 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-1471: SnakeYaml Constructor Deserialization Remote Code Execution 8.3 high 2.0 12 Dec 2022
CVE-2017-18640: SnakeYAML Entity Expansion during load operation 7.5 high 1.26 04 Jun 2021
CVE-2022-25857: Uncontrolled Resource Consumption in snakeyaml 7.5 high 1.31 31 Aug 2022
CVE-2022-38752: Denial of Service in snakeYAML before 1.32 6.5 medium 1.32 06 Sep 2022
CVE-2022-38751: Denial of Service in snakeYAML 6.5 medium 1.31 06 Sep 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About org.yaml:snakeyaml

Is org.yaml:snakeyaml safe to use?

Vulert records 9 vulnerabilities for org.yaml:snakeyaml in Maven: 0 critical, 3 high, 6 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is org.yaml:snakeyaml's Vulert package health score?

Vulert scores org.yaml:snakeyaml 76/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of org.yaml:snakeyaml affected?

No. 2.7, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of org.yaml:snakeyaml should I use?

2.7 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does org.yaml:snakeyaml have?

9 vulnerabilities are recorded for org.yaml:snakeyaml in the Maven ecosystem: 0 critical, 3 high, 6 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.yaml:snakeyaml vulnerabilities disclosed?

0 vulnerabilities were recorded for org.yaml:snakeyaml in the last 12 months, and the oldest entry in this database dates to 04 Jun 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of org.yaml:snakeyaml are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor org.yaml:snakeyaml for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.yaml:snakeyaml version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.