CVE-2022-1471

CRITICALNVD 8.39.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because EPSS predicted 99.5% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 8.3 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Weaponized

Also known asEUVD-2022-7690 (ENISA EUVD) · GHSA-mjmj-j48q-9wg2 (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 99.5%
  • Public exploit code is available (Metasploit, other public proof-of-concept code)
CISA-KEV: Not listedEPSS PROB: 99.5%CVSS: 8.3Exploit: Metasploit · other public PoCExposed services: Not assessed

A fix is available — apply it.

SnakeYaml's Constructor() class does not restrict types which can be instantiated during deserialization. Deserializing yaml content provided by an attacker can lead to remote code execution. We recommend using SnakeYaml's SafeConsturctor when parsing untrusted content to restrict deserialization. We recommend upgrading to version 2.0 and beyond.

CVSS v3
8.3
EG Score
9.0CRITICALhigh confidence
EG Risk
77
EG Risk 77/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity83% × 45%
Impact severity (EG Severity): CVSS 8.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation99.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
99.5%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 8.3 HIGH): a likelihood of exploitation, not impact.

EG Severity
8.3 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
99.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

December 1, 2022

Last Modified

June 18, 2025

Advisory Details (8)

Auto-updated Sep 6, 2026
Patch available. Sources: github.
Web page

GitHub - mbechler/marshalsec · GitHub

https://github.com/mbechler/marshalsec
GitHub advisoryMentions a patch (unverified)

SnakeYaml: Constructor Deserialization Remote Code Execution · Advisory · google/security-research · GitHub

https://github.com/google/security-research/security/advisories/GHSA-mjmj-j48q-9wg2
Web page

CVE-2022-1471 - SnakeYAML library RCE Vulnerability impacts Multiple Products | Atlassian Support | Atlassian Documentation

https://confluence.atlassian.com/security/cve-2022-1471-snakeyaml-library-rce-vulnerability-in-multiple-products-1296171009.html
Web page

oss-security - CVE-2023-46302: Apache Submarine: Fix CVE-2022-1471 SnakeYaml unsafe deserialization

http://www.openwall.com/lists/oss-security/2023/11/19/1

Patch Availability(24)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhateap7-snakeyaml-0:1.33.0-1.SP1_redhat_00001.1.el7eap2025-02-24redhat
redhateap7-snakeyaml-0:1.33.0-1.SP1_redhat_00001.1.ep7.el72025-02-24redhat
redhatsnakeyaml2024-03-18redhat
redhatjenkins-2-plugins-0:4.11.1706516946-1.el82024-02-12redhat
redhatredhat-openjdk-18/openjdk18-openshift:1.17-12024-01-22redhat
redhatjenkins-2-plugins-0:4.11.1698299029-1.el82023-10-30redhat
redhatpatch2023-09-14redhat
redhatdevspaces/udi-rhel8:3.6-202023-05-18redhat
redhatjenkins-2-plugins-0:4.11.1683009941-1.el82023-05-17redhat
redhatcandlepin-0:4.2.13-1.el8sat2023-05-03redhat
redhateap7-snakeyaml-0:1.33.0-2.SP1_redhat_00001.1.el7eap2023-03-29redhat
redhateap7-snakeyaml-0:1.33.0-2.SP1_redhat_00001.1.el8eap2023-03-29redhat
redhatorg.yaml/snakeyaml:1.33.0.SP1-redhat-000012023-03-29redhat
redhateap7-snakeyaml-0:1.33.0-2.SP1_redhat_00001.1.el9eap2023-03-29redhat
redhatrh-sso7-keycloak-0:18.0.6-1.redhat_00001.1.el7sso2023-03-01redhat
redhatrh-sso-7/sso76-openshift-rhel8:7.6-202023-03-01redhat
redhatrh-sso7-keycloak-0:18.0.6-1.redhat_00001.1.el8sso2023-03-01redhat
redhatrh-sso7-keycloak-0:18.0.6-1.redhat_00001.1.el9sso2023-03-01redhat
redhatjenkins-2-plugins-0:4.9.1675668922-1.el82023-02-23redhat
redhatjenkins-2-plugins-0:4.10.1675407676-1.el82023-02-15redhat
redhatpatch2023-02-14redhat
redhatubi8/openjdk-8-runtime:1.14-102023-01-04redhat
redhatprometheus-jmx-exporter-0:0.12.0-9.el8_72022-12-15redhat
mavenorg.yaml:snakeyaml @ 2.0 (fixes <= 1.33)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
snakeyaml1.28-1 ... 2.5+ds-1~exp0 (12 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
snakeyaml1.33-2 ... 2.5+ds-1~exp0 (6 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
snakeyaml2.0+ds+really1.33-1, 2.4+ds-1~exp0, 2.5+ds-1, 2.5+ds-1~exp0
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
snakeyaml2.0+ds+really1.33-1, 2.4+ds-1~exp0, 2.5+ds-1, 2.5+ds-1~exp0
  • every version on: no fix on record
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.yaml:snakeyaml1.10 ... 1.9 (30 versions)
  • every version up to 2.0: fixed in 2.0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(8)

Data Freshness Timeline

(refreshed 12× in last 7d / 45× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 114 rows on record for this CVE, as 97 entries (3 repeats merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 14 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:02 UTCEchelonGraph re-scored
  2. 2026-11-12 16:02 UTCVendor advisory
  3. 2026-11-12 16:02 UTCGHSA enrichmentGHSA-mjmj-j48q-9wg2 · GitHub severity HIGH · GitHub CVSS 8.3
  4. 2026-11-11 15:39 UTCEchelonGraph re-scored
  5. 2026-11-11 15:39 UTCVendor advisory
  6. 2026-11-11 15:39 UTCGHSA enrichmentGHSA-mjmj-j48q-9wg2 · GitHub severity HIGH · GitHub CVSS 8.3
  7. 2026-11-10 15:18 UTCEchelonGraph re-scored
  8. 2026-11-10 15:18 UTCVendor advisory
  9. 2026-11-10 15:18 UTCGHSA enrichmentGHSA-mjmj-j48q-9wg2 · GitHub severity HIGH · GitHub CVSS 8.3
  10. 2026-11-09 14:55 UTCEchelonGraph re-scored
  11. 2026-11-09 14:55 UTCGHSA enrichmentGHSA-mjmj-j48q-9wg2 · GitHub severity HIGH · GitHub CVSS 8.3
  12. 2026-11-08 14:34 UTCEchelonGraph re-scored
  13. 2026-11-08 14:34 UTCGHSA enrichmentGHSA-mjmj-j48q-9wg2 · GitHub severity HIGH · GitHub CVSS 8.3
  14. 2026-11-07 14:13 UTCEchelonGraph re-scored
  15. 2026-11-07 14:13 UTCVendor advisory
  16. 2026-11-07 14:13 UTCGHSA enrichmentGHSA-mjmj-j48q-9wg2 · GitHub severity HIGH · GitHub CVSS 8.3
  17. 2026-11-06 13:51 UTCEchelonGraph re-scored
  18. 2026-11-06 13:51 UTCVendor advisory
  19. 2026-11-06 13:51 UTCGHSA enrichmentGHSA-mjmj-j48q-9wg2 · GitHub severity HIGH · GitHub CVSS 8.3
  20. 2026-11-05 13:30 UTCEchelonGraph re-scored
  21. 2026-11-05 13:30 UTCVendor advisory
  22. 2026-11-05 13:30 UTCGHSA enrichmentGHSA-mjmj-j48q-9wg2 · GitHub severity HIGH · GitHub CVSS 8.3
  23. 2026-11-04 16:30 UTCEPSS rescoreEPSS 99.5% · 99th percentile
  24. 2026-11-04 13:08 UTCEchelonGraph re-scored
  25. 2026-11-04 13:08 UTCVendor advisory
Show 72 more
  1. 2026-11-04 13:08 UTCGHSA enrichmentGHSA-mjmj-j48q-9wg2 · GitHub severity HIGH · GitHub CVSS 8.3
  2. 2026-11-03 22:55 UTCOSV refresh
  3. 2026-11-03 12:45 UTCEchelonGraph re-scored
  4. 2026-11-03 12:45 UTCVendor advisory
  5. 2026-11-03 12:45 UTCGHSA enrichmentGHSA-mjmj-j48q-9wg2 · GitHub severity HIGH · GitHub CVSS 8.3
  6. 2026-11-02 12:24 UTCEchelonGraph re-scored
  7. 2026-11-02 12:24 UTCVendor advisory
  8. 2026-11-02 12:24 UTCGHSA enrichmentGHSA-mjmj-j48q-9wg2 · GitHub severity HIGH · GitHub CVSS 8.3
  9. 2026-11-01 12:03 UTCVendor advisory
  10. 2026-11-01 12:03 UTCGHSA enrichmentGHSA-mjmj-j48q-9wg2 · GitHub severity HIGH · GitHub CVSS 8.3
  11. 2026-11-01 08:29 UTCGHSA enrichmentGHSA-mjmj-j48q-9wg2 · GitHub severity HIGH · GitHub CVSS 8.3
  12. 2026-11-01 08:29 UTCEchelonGraph re-scored
  13. 2026-10-31 16:29 UTCEPSS rescoreEPSS 99.5% · 99th percentile
  14. 2026-10-31 11:41 UTCEchelonGraph re-scored
  15. 2026-10-31 11:41 UTCVendor advisory
  16. 2026-10-30 11:20 UTCEchelonGraph re-scored
  17. 2026-10-30 11:20 UTCVendor advisory
  18. 2026-10-29 10:59 UTCEchelonGraph re-scored
  19. 2026-10-29 10:59 UTCVendor advisory
  20. 2026-10-28 10:25 UTCEchelonGraph re-scored
  21. 2026-10-28 10:25 UTCVendor advisory
  22. 2026-10-27 09:10 UTCEchelonGraph re-scored
  23. 2026-10-27 09:10 UTCVendor advisory
  24. 2026-10-26 07:59 UTCVendor advisory
  25. 2026-10-25 18:16 UTCEchelonGraph re-scored
  26. 2026-10-25 16:29 UTCEPSS rescoreEPSS 99.5% · 99th percentile
  27. 2026-10-25 07:36 UTCEchelonGraph re-scored
  28. 2026-10-25 07:36 UTCVendor advisory
  29. 2026-10-24 07:15 UTCEchelonGraph re-scored
  30. 2026-10-24 07:15 UTCVendor advisory
  31. 2026-10-23 06:53 UTCEchelonGraph re-scored
  32. 2026-10-23 06:53 UTCVendor advisory
  33. 2026-10-22 06:32 UTCEchelonGraph re-scored
  34. 2026-10-22 06:32 UTCVendor advisory
  35. 2026-10-21 06:06 UTCEchelonGraph re-scored
  36. 2026-10-21 06:06 UTCVendor advisory
  37. 2026-10-20 05:43 UTCEchelonGraph re-scored
  38. 2026-10-20 05:43 UTCVendor advisory
  39. 2026-10-19 05:20 UTCEchelonGraph re-scored
  40. 2026-10-19 05:20 UTCVendor advisory
  41. 2026-10-18 04:58 UTCEchelonGraph re-scored
  42. 2026-10-18 04:58 UTCVendor advisory
  43. 2026-10-17 04:34 UTCEchelonGraph re-scored
  44. 2026-10-17 04:34 UTCVendor advisory
  45. 2026-10-16 04:12 UTCEchelonGraph re-scored
  46. 2026-10-16 04:12 UTCVendor advisory
  47. 2026-10-15 01:24 UTCEchelonGraph re-scored
  48. 2026-10-15 01:24 UTCVendor advisory
  49. 2026-10-14 16:29 UTCEPSS rescoreEPSS 99.6% · 99th percentile
  50. 2026-10-13 22:18 UTCEchelonGraph re-scored
  51. 2026-10-13 22:18 UTCVendor advisory
  52. 2026-10-12 19:04 UTCVendor advisory
  53. 2026-10-12 19:03 UTCEchelonGraph re-scored
  54. 2026-10-11 23:29 UTCEchelonGraph re-scored
  55. 2026-10-02 16:23 UTCEPSS rescoreEPSS 99.6% · 99th percentile
  56. 2026-09-30 15:47 UTCEchelonGraph re-scored
  57. 2026-09-24 14:00 UTCEPSS rescoreEPSS 99.6% · 99th percentile
  58. 2026-09-24 05:15 UTCOSV refresh
  59. 2026-09-16 14:05 UTCEPSS rescoreEPSS 99.6% · 99th percentile
  60. 2026-09-05 15:25 UTCEPSS rescoreEPSS 99.6% · 99th percentile
  61. 2026-09-04 22:24 UTCOSV refresh
  62. 2026-08-30 19:14 UTCEPSS rescoreEPSS 99.6% · 99th percentile
  63. 2026-08-30 01:19 UTCEPSS rescoreEPSS 99.6% · 99th percentile
  64. 2026-08-24 14:13 UTCEPSS rescoreEPSS 99.6% · 99th percentile
  65. 2026-08-18 09:34 UTCOSV refresh
  66. 2026-08-12 13:48 UTCEPSS rescoreEPSS 99.6% · 99th percentile
  67. 2026-08-03 04:57 UTCOSV refresh
  68. 2026-07-24 14:15 UTCEPSS rescoreEPSS 99.6% · 99th percentile
  69. 2026-07-23 02:07 UTCEchelonGraph re-scored
  70. 2026-07-22 22:53 UTCEchelonGraph re-scored
  71. 2026-07-16 14:19 UTCOSV refresh
  72. 2026-07-09 19:07 UTCEPSS rescoreEPSS 99.6% · 99th percentile

Publicly available exploits

(3 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 2 GitHub PoCs). Defenders should treat patch urgency accordingly.

  • Metasploitexploit/multi/http/torchserver_cve_2023_43654✓ verified
    Published Oct 12, 2023

    PyTorch Model Server Registration and Deserialization RCE

    Open source ↗
  • GitHub PoCfalconkei/snakeyaml_cve_poc
    Published May 8, 2023

    SnakeYAML-CVE-2022-1471-POC

    Open source ↗
  • GitHub PoC1fabunicorn/SnakeYAML-CVE-2022-1471-POC
    Published Mar 2, 2023

    Code for veracode blog

    Open source ↗

Frequently asked(5)

What is CVE-2022-1471?
CVE-2022-1471 is a critical-severity vulnerability; its CVE record was published on December 1, 2022. SnakeYaml's Constructor() class does not restrict types which can be instantiated during deserialization. Deserializing yaml content provided by an attacker can lead to remote code execution. We recommend using SnakeYaml's SafeConsturctor when parsing untrusted content to restrict deserialization.…
When was the CVE record for CVE-2022-1471 published?
The CVE record for CVE-2022-1471 was published on December 1, 2022. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 18, 2025; the record at its source may have been updated since.
Is CVE-2022-1471 actively exploited?
CVE-2022-1471 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it, and CISA's SSVC data says a public PoC exists and its EPSS is 50% or more. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 99.5% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-1471?
CVE-2022-1471 has a CVSS v3 base score of 8.3 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
How do I remediate CVE-2022-1471?
A fix for CVE-2022-1471 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-1471 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-1471

Explore →

Is Your Infrastructure Affected by CVE-2022-1471?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.