Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven
Not in CISA KEV
HIGH severity

CVE-2022-25857 snakeyaml

HIGHFix: snakeyaml/snakeyaml@fc30078

CVE-2022-25857 is a high-severity (CVSS 7.5) CWE-776 vulnerability in org.yaml:snakeyaml. 2 public exploit references exist, so weaponization risk is real. A fix is available for org.yaml:snakeyaml — see the affected versions and patch details below.

Denial of Service (DoS)

Also known asGHSA-3mc7-4q67-w48m
Published
Aug 30, 2022
Updated
Aug 12, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Sep 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs86th percentile — riskier than 86% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2022-25857 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

1 pkg affected
org.yaml:snakeyaml

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.yaml:snakeyamlall versions1.31org.yaml:snakeyaml:1.31
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.yaml:snakeyaml, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.yaml:snakeyaml to 1.31 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-25857 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-25857 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2022-25857. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

For RHEL-8 it's downgraded to moderate because "snakeyaml" itself in RHEL 8 or RHEL-9 isn't shipped and "prometheus-jmx-exporter" is needed as build dependency. And it's not directly exploitable, hence severity marked as moderate. Red Hat Integration and AMQ products are not vulnerable to this flaw, so their severity…

ProductFixed inAdvisory
OCP-Tools-4.12-RHEL-8jenkins-2-plugins-0:4.12.1698294000-1.el8RHSA-2023:6172
OCP-Tools-4.12-RHEL-8jenkins-2-plugins-0:4.12.1706515741-1.el8RHSA-2024:0778
OCP-Tools-4.13-RHEL-8jenkins-2-plugins-0:4.13.1698292274-1.el8RHSA-2023:6179
OCP-Tools-4.13-RHEL-8jenkins-2-plugins-0:4.13.1706516346-1.el8RHSA-2024:0776
OCP-Tools-4.14-RHEL-8jenkins-2-plugins-0:4.14.1699356715-1.el8RHSA-2023:7288
OCP-Tools-4.14-RHEL-8jenkins-2-plugins-0:4.14.1706516441-1.el8RHSA-2024:0777
OpenShift Developer Tools and Services for OCP 4.11jenkins-2-plugins-0:4.11.1683009941-1.el8RHSA-2023:3198
Red Hat AMQ Broker 7snakeyamlRHSA-2022:8876

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2022-25857 in your dependencies?

O3 Security finds CVE-2022-25857 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2022-25857: snakeyaml DoS (High 7.5) | O3 Security