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

CVE-2022-38752 snakeyaml

MEDIUM

CVE-2022-38752 is a medium-severity (CVSS 6.5) CWE-121 vulnerability in org.yaml:snakeyaml. A fix is available for org.yaml:snakeyaml — see the affected versions and patch details below.

DoS in SnakeYAML

Also known asGHSA-9w3m-gqgf-c4p9
Published
Sep 5, 2022
Updated
Aug 12, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Sep 18, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-38752.

EPSS Exploitation Probability

via FIRST.org ↗
2.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs84th percentile — riskier than 84% 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-38752 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 377,166 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

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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.yaml:snakeyamlall versions1.32org.yaml:snakeyaml:1.32

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.32 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-38752 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-38752 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2022-38752. 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 HatModerate

Red Hat Build of Quarkus is not affected by this issue as it already includes the fixed version.

ProductFixed inAdvisory
Red Hat AMQ Streams 2.3.0snakeyamlRHSA-2023:0189
Red Hat build of Eclipse Vert.x 4.3.3snakeyamlRHSA-2022:6757
Red Hat Data Grid 8.4.0snakeyamlRHSA-2022:8524
Red Hat JBoss Enterprise Application Platform 7snakeyamlRHSA-2023:1516
Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 8eap7-snakeyaml-0:1.33.0-2.SP1_redhat_00001.1.el8eapRHSA-2023:1513
Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 9eap7-snakeyaml-0:1.33.0-2.SP1_redhat_00001.1.el9eapRHSA-2023:1514
Red Hat JBoss Enterprise Application Platform 7.4 on RHEL 7eap7-snakeyaml-0:1.33.0-2.SP1_redhat_00001.1.el7eapRHSA-2023:1512
Red Hat Satellite 6.13 for RHEL 8candlepin-0:4.2.13-1.el8satRHSA-2023:2097

Frequently Asked Questions

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

Is CVE-2022-38752 in your dependencies?

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

CVE-2022-38752: snakeyaml (Medium 6.5) | O3 Security