CVE-2022-32224

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 2.4%, top 18% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 9.8Exploit: Elevated riskExposed: 0

A fix is available — apply it.

A possible escalation to RCE vulnerability exists when using YAML serialized columns in Active Record < 7.0.3.1, <6.1.6.1, <6.0.5.1 and <5.2.8.1 which could allow an attacker, that can manipulate data in the database (via means like SQL injection), the ability to escalate to an RCE.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
75(Attend)
EG Risk 75/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
2%
EPSS %ILE
84%
KEV
Not listed

Published

December 5, 2022

Last Modified

May 11, 2026

Advisory Details (3)

Auto-updated Sep 16, 2026
Patch available. Sources: github.
generic Patch Available

[SECURITY] [DLA 4578-1] rails security update

https://lists.debian.org/debian-lts-announce/2026/05/msg00022.html
generic
https://groups.google.com/g/rubyonrails-security/c/MmFO3LYQE8U
github Patch Available

Active Record RCE bug with Serialized Columns · CVE-2022-32224 · GitHub Advisory Database · GitHub

https://github.com/advisories/GHSA-3hhc-qp5v-9p2j

Vendor Advisories for CVE-2022-32224(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhattfm-rubygem-activerecord-0:6.1.7-1.el8sat2023-05-03redhat
redhattfm-rubygem-activerecord-0:6.0.6-2.el8sat2023-03-07redhat

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 rangeFixed inDependents
rails2:6.0.3.7+dfsg-2, 2:6.0.3.7+dfsg-2+deb11u1, 2:6.0.3.7+dfsg-2+deb11u2, 2:6.0.3.7+dfsg-2+deb11u3, 2:6.0.3.7+dfsg-2+deb11u42:6.0.3.7+dfsg-2+deb11u5—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
rails—2:6.1.6.1+dfsg-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
rails—2:6.1.6.1+dfsg-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
rails—2:6.1.6.1+dfsg-1—
RubyGems(1)
PackageVulnerable rangeFixed inDependents
activerecord1.0.0 ... 5.2.8 (362 versions)5.2.8.1—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 6× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 210 total refreshes for this CVE.

  1. 2026-09-18 19:24 UTCEPSS rescore
  2. 2026-09-16 14:05 UTCEPSS rescore
  3. 2026-09-15 03:06 UTCEPSS rescore
  4. 2026-09-14 19:14 UTCOSV refresh
  5. 2026-09-13 16:44 UTCEPSS rescore
  6. 2026-09-12 14:57 UTCEPSS rescore
  7. 2026-09-11 14:49 UTCEPSS rescore
  8. 2026-09-11 09:33 UTCEPSS rescore
  9. 2026-09-08 21:57 UTCEPSS rescore
  10. 2026-09-07 15:58 UTCEPSS rescore
  11. 2026-09-06 13:45 UTCEPSS rescore
  12. 2026-09-05 15:25 UTCEPSS rescore
  13. 2026-09-04 13:57 UTCEPSS rescore
  14. 2026-09-04 13:57 UTCEPSS rescore
  15. 2026-09-04 05:04 UTCEPSS rescore
  16. 2026-09-02 14:09 UTCEPSS rescore
  17. 2026-09-01 13:51 UTCEPSS rescore
  18. 2026-08-30 19:14 UTCEPSS rescore
  19. 2026-08-30 01:19 UTCEPSS rescore
  20. 2026-08-28 21:38 UTCEPSS rescore
  21. 2026-08-27 14:22 UTCEPSS rescore
  22. 2026-08-26 18:46 UTCOSV refresh
  23. 2026-08-26 14:43 UTCEPSS rescore
  24. 2026-08-25 13:46 UTCEPSS rescore
  25. 2026-08-24 14:13 UTCEPSS rescore
Show 75 more
  1. 2026-08-23 00:16 UTCEPSS rescore
  2. 2026-08-21 23:46 UTCEPSS rescore
  3. 2026-08-20 22:52 UTCEPSS rescore
  4. 2026-08-19 17:01 UTCEPSS rescore
  5. 2026-08-18 13:45 UTCEPSS rescore
  6. 2026-08-17 13:44 UTCEPSS rescore
  7. 2026-08-16 14:53 UTCEPSS rescore
  8. 2026-08-16 02:11 UTCEPSS rescore
  9. 2026-08-15 01:27 UTCEPSS rescore
  10. 2026-08-13 21:57 UTCEPSS rescore
  11. 2026-08-12 13:48 UTCEPSS rescore
  12. 2026-08-11 13:38 UTCEPSS rescore
  13. 2026-08-10 09:09 UTCOSV refresh
  14. 2026-08-08 16:34 UTCEPSS rescore
  15. 2026-08-07 16:24 UTCEPSS rescore
  16. 2026-08-06 13:44 UTCEPSS rescore
  17. 2026-08-05 19:15 UTCEPSS rescore
  18. 2026-08-04 15:07 UTCEPSS rescore
  19. 2026-08-04 10:35 UTCEPSS rescore
  20. 2026-08-03 10:33 UTCEPSS rescore
  21. 2026-08-02 02:24 UTCEPSS rescore
  22. 2026-08-01 04:13 UTCEPSS rescore
  23. 2026-07-30 16:25 UTCEPSS rescore
  24. 2026-07-30 01:28 UTCEPSS rescore
  25. 2026-07-28 15:33 UTCEPSS rescore
  26. 2026-07-26 14:52 UTCEPSS rescore
  27. 2026-07-25 14:15 UTCEPSS rescore
  28. 2026-07-25 09:41 UTCOSV refresh
  29. 2026-07-24 14:15 UTCEPSS rescore
  30. 2026-07-24 14:15 UTCEPSS rescore
  31. 2026-07-23 14:16 UTCEPSS rescore
  32. 2026-07-23 14:16 UTCEPSS rescore
  33. 2026-07-23 02:11 UTCEG score recompute
  34. 2026-07-22 22:58 UTCEG score recompute
  35. 2026-07-22 14:06 UTCEPSS rescore
  36. 2026-07-22 14:06 UTCEPSS rescore
  37. 2026-07-21 15:22 UTCEPSS rescore
  38. 2026-07-21 15:22 UTCEPSS rescore
  39. 2026-07-20 17:05 UTCEPSS rescore
  40. 2026-07-19 14:29 UTCEPSS rescore
  41. 2026-07-19 02:27 UTCEPSS rescore
  42. 2026-07-19 02:27 UTCEPSS rescore
  43. 2026-07-18 10:03 UTCEPSS rescore
  44. 2026-07-18 10:02 UTCEPSS rescore
  45. 2026-07-16 17:00 UTCEPSS rescore
  46. 2026-07-15 16:56 UTCEPSS rescore
  47. 2026-07-15 16:56 UTCEPSS rescore
  48. 2026-07-15 01:58 UTCEPSS rescore
  49. 2026-07-15 01:58 UTCEPSS rescore
  50. 2026-07-13 22:27 UTCEPSS rescore
  51. 2026-07-13 06:11 UTCEPSS rescore
  52. 2026-07-13 06:11 UTCEPSS rescore
  53. 2026-07-12 05:44 UTCEPSS rescore
  54. 2026-07-12 05:44 UTCEPSS rescore
  55. 2026-07-11 08:25 UTCEPSS rescore
  56. 2026-07-11 08:25 UTCEPSS rescore
  57. 2026-07-09 19:07 UTCEPSS rescore
  58. 2026-07-08 15:12 UTCEPSS rescore
  59. 2026-07-08 04:05 UTCOSV refresh
  60. 2026-07-07 13:44 UTCEPSS rescore
  61. 2026-07-06 16:25 UTCEPSS rescore
  62. 2026-07-06 16:25 UTCEPSS rescore
  63. 2026-07-06 02:21 UTCEPSS rescore
  64. 2026-07-06 02:21 UTCEPSS rescore
  65. 2026-07-05 02:28 UTCEPSS rescore
  66. 2026-07-05 02:28 UTCEPSS rescore
  67. 2026-07-04 06:29 UTCEPSS rescore
  68. 2026-07-04 06:29 UTCEPSS rescore
  69. 2026-07-01 15:04 UTCEPSS rescore
  70. 2026-06-30 23:20 UTCEPSS rescore
  71. 2026-06-30 23:20 UTCEPSS rescore
  72. 2026-06-28 14:06 UTCEPSS rescore
  73. 2026-06-28 04:54 UTCEPSS rescore
  74. 2026-06-27 03:07 UTCEPSS rescore
  75. 2026-06-25 13:48 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCooooooo-q/cve-2022-32224-rails
    First seen Jul 17, 2022
    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-32224?
CVE-2022-32224 is a critical vulnerability published on December 5, 2022. A possible escalation to RCE vulnerability exists when using YAML serialized columns in Active Record < 7.0.3.1, <6.1.6.1, <6.0.5.1 and <5.2.8.1 which could allow an attacker, that can manipulate data in the database (via means like SQL injection), the ability to escalate to an RCE.
When was CVE-2022-32224 disclosed?
CVE-2022-32224 was first published in the National Vulnerability Database on December 5, 2022, with the most recent update on May 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-32224 actively exploited?
CVE-2022-32224 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 16.3% of all scored CVEs.
What is the CVSS score of CVE-2022-32224?
CVE-2022-32224 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2022-32224?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-32224, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2022-32224?

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

Start Free Scan →Browse All CVEs