CVE-2022-32224

Exp

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.

Published: 2022-12-05 Last update: 2026-05-11 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-32224 is rated High Exploit Risk (83.5/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 1.94%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2022-32224

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2022-32224

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-02 2.00% 1.94% -0.05%
2 2026-05-31 1.90% 2.00% +0.10%
3 2026-05-19 — 1.90% —

Full EPSS history (55 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-32224

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2022-32224

GitHub Security Advisory for CVE-2022-32224

GHSA-3hhc-qp5v-9p2j · Severity: critical · Ecosystem: rubygems — Active Record RCE bug with Serialized Columns

OS Trackers for CVE-2022-32224

vendor priority summary link
debian not yet assigned CVE-2022-32224 not yet assigned priority: Debian including 1 source packages (rails), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2022-32224
gentoo normal CVE-2022-32224: 1 GLSA(s) (202408-24), 1 atom(s) (dev-ruby/rails); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2022-32224
redhat critical — https://access.redhat.com/security/cve/CVE-2022-32224
suse high — https://www.suse.com/security/cve/CVE-2022-32224/
ubuntu medium CVE-2022-32224 medium priority: Ubuntu including 7 source packages (rails, rails-4.0, …), 91 status rows across 13 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 73, needs-triage 13, ignored 5. https://ubuntu.com/security/CVE-2022-32224

Affected software / configurations for CVE-2022-32224

Vendor Product Version Raw CPE
activerecord_project activerecord < 5.2.8.1 cpe:2.3:a:activerecord_project:activerecord:*:*:*:*:*:ruby:*:*
activerecord_project activerecord >= 6.0.0, < 6.0.5.1 cpe:2.3:a:activerecord_project:activerecord:*:*:*:*:*:ruby:*:*
activerecord_project activerecord >= 6.1.0, < 6.1.6.1 cpe:2.3:a:activerecord_project:activerecord:*:*:*:*:*:ruby:*:*
activerecord_project activerecord >= 7.0.0, < 7.0.3.1 cpe:2.3:a:activerecord_project:activerecord:*:*:*:*:*:ruby:*:*

References for CVE-2022-32224

cvelogic Threat Intelligence