Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

CVE-2022-38749

MEDIUM

CVE-2022-38749 is a medium-severity (CVSS 6.5) CWE-121 vulnerability in org.yaml:snakeyaml. O3 Security confirms whether CVE-2022-38749 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

DoS in SnakeYAML

Also known asGHSA-c4r9-r8fh-9vj2
Published
Sep 5, 2022
Updated
Jul 15, 2026
Affected
7 pkgs
Patched
1 / 7
Exploits
None indexed

Blast Radius

7 pkgs affected
org.yaml:snakeyamlbe.cylab:snakeyamlcom.alipay.sofa.acts:acts-common-utilio.prometheus.jmx:jmx_prometheus_httpserverio.prometheus.jmx:jmx_prometheus_httpserver_java6org.testifyproject.external:external-snakeyamlpl.droidsonroids.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 stackoverflow.

Affected Packages

7 total 1 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.yaml:snakeyamlall versions1.31
Mavenbe.cylab:snakeyamlall versionsNo fix
Mavencom.alipay.sofa.acts:acts-common-utilall versionsNo fix
Mavenio.prometheus.jmx:jmx_prometheus_httpserverall versionsNo fix
Mavenio.prometheus.jmx:jmx_prometheus_httpserver_java6all versionsNo fix
Mavenorg.testifyproject.external:external-snakeyamlall versionsNo fix

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  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-38749 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 pinpoints whether CVE-2022-38749 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

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

Is CVE-2022-38749 in your dependencies?

O3 detects CVE-2022-38749 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.