CVE-2022-21831 is a critical-severity (CVSS 9.8) Code Injection vulnerability in activestorage. A fix is available for activestorage — see the affected versions and patch details below.
Possible code injection vulnerability in Rails / Active Storage
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2022-21831 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
activestorage💎activestorage💎activestorage💎activestorageReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.
Description
The Active Storage module of Rails starting with version 5.2.0 is possibly vulnerable to code injection. This issue was patched in versions 5.2.6.3, 6.0.4.7, 6.1.4.7, and 7.0.2.3. To work around this issue, applications should implement a strict allow-list on accepted transformation methods or arguments. Additionally, a strict ImageMagick security policy will help mitigate this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 💎RubyGems | activestorage | ≥ 5.2.0&&< 5.2.6.3 | 5.2.6.3bundle update activestorage --conservative |
| 💎RubyGems | activestorage | ≥ 6.0.0&&< 6.0.4.7 | 6.0.4.7bundle update activestorage --conservative |
| 💎RubyGems | activestorage | ≥ 6.1.0&&< 6.1.4.7 | 6.1.4.7bundle update activestorage --conservative |
| 💎RubyGems | activestorage | ≥ 7.0.0&&< 7.0.2.3 | 7.0.2.3bundle update activestorage --conservative |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for activestorage, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update activestorage to 5.2.6.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-21831 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-21831 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2022-21831. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2022-21831 in your dependencies?
O3 Security finds CVE-2022-21831 across RubyGems dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.