CVE-2026-122006 The activestorage gem before 8.1.4.1 for Ruby on Rails, when ImageMagick attachment processing occurs, can allow server read and write opera
Critical 9.8
Published
Updated
Check this codebase for CVE-2026-122006 and fix it if it is affected.
What it is: CVE-2026-122006 is a critical vulnerability in rubyonrails Active Storage, published on 4 Nov 2026.
Exploitation: There is no known exploitation of CVE-2026-122006 in the wild and no public exploit code.
Affected product: rubyonrails Active Storage. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-122006/ (Markdown: https://insights.sbomify.com/CVE-2026-122006/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2026-122006?
CVE-2026-122006 is a critical vulnerability in rubyonrails Active Storage, published on 4 Nov 2026.
Official description
The activestorage gem before 8.1.4.1 for Ruby on Rails, when ImageMagick attachment processing occurs, can allow server read and write operations (e.g., reading secret_key_base) because the ImageMagick analyzer runs when a file is attached, and there is not an ImageMagick security policy to block unintended functionality.
Weakness: CWE-1188
Which versions are affected by CVE-2026-122006?
How do I fix CVE-2026-122006?
Upgrade to a fixed version.
Is CVE-2026-122006 being exploited?
There is no known exploitation of CVE-2026-122006 in the wild and no public exploit code.
Public exploit code: 1 proofs of concept on GitHub.
Sources
Also known as DEBIAN-CVE-2026-122006, UBUNTU-CVE-2026-122006.