Advisory record · GHSA-c4r9-r8fh-9vj2

snakeYAML before 1.31 vulnerable to Denial of Service due to Out-of-bounds Write

CVSS 6.5 MediumEPSS 0.022 · 82nd percentile

Published by the GitHub Advisory Database at 6 Sept 2022, 00:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.yaml:snakeyamlMaven<1.311.31
be.cylab:snakeyamlMaven=1.25.1No fixed version yet
com.alipay.sofa.acts:acts-common-utilMaven=1.0.0No fixed version yet
io.prometheus.jmx:jmx_prometheus_httpserverMaven=0.17.0No fixed version yet
io.prometheus.jmx:jmx_prometheus_httpserver_java6Maven<=0.18.0No fixed version yet
org.testifyproject.external:external-snakeyamlMaven<=1.0.6No fixed version yet
pl.droidsonroids.yaml:snakeyamlMaven<=1.18.2No fixed version yet
Identifiers
GHSA-c4r9-r8fh-9vj2 · CVE-2022-38749
Weakness (CWE)
CWE-121 · CWE-787
Published
6 Sept 2022
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

snakeYAML versions before 1.31 can be crashed by parsing untrusted YAML, since a crafted document causes a stack overflow. Upgrade org.yaml:snakeyaml to 1.31 or later. Other listed packages, including be.cylab:snakeyaml, have no fixed version listed, so avoid parsing untrusted input with them.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.5 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H CNA (Google)
  • CISA KEV Not listed.
  • EPSS 0.022, the 82nd percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:18 UTC First seen by agentprime
  2. 31 Oct 2026, 14:18 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.