An unauthenticated uploader may cause arbitrary file writes. Applications using the Disk storage service may also expose files readable by the application process.The Rails advisory displays CVE-2026-126082 for this issue. NVD marks that identifier rejected as a duplicate and links the same advisory from its CVE-2026-122006 record. This profile uses CVE-2026-122006 as the active identifier.
What it allows
How Does CVE-2026-122006 Affect Active Storage?
ImageMagick chooses a coder from attachment contents. Rails says some coders act on files named inside an image, and Active Storage had not constrained them. Its analyzer runs when a file is attached, so a crafted upload can reach ImageMagick without a separate preview request.
Rails says an unauthenticated attacker may write arbitrary server files. With Disk storage, the attacker may also read files accessible to the application process, including secrets. Those secrets could enable further access or code execution. This is a potential consequence, not a verified incident.
Brandefense Blackhole counted four dark chat posts matching CVE-2026-122006 from August 15 through November 13, 2026. The unit is posts, and the count does not establish exploitation. Teams assessing exposed applications can review the vulnerability intelligence platform while prioritizing fixes.
GitHub search found one public repository whose name contains CVE-2026-122006 on November 13, 2026. The unit is repository names, not verified proof of concept code. CISA's November 10, 2026 KEV catalog did not list either identifier.
The related Rails Active Storage security news report gives the disclosure context. The vulnerability intelligence glossary explains the broader prioritization concept.
Who is affected
Which Versions and Configurations Does CVE-2026-122006 Affect?
Rails lists activestorage versions below 8.0.5.2 and versions from 8.1 up to, but excluding, 8.1.4.1. The fixed releases are 8.0.5.2 and 8.1.4.1. Confirm the installed gem version and the application's running version after updating.
All three Rails conditions must apply: Active Storage uses ImageMagick, the ImageMagick policy permits the relevant coders, and untrusted users can upload files. The :mini_magick variant processor uses ImageMagick; Rails says it is the default with load_defaults 6.1 or earlier. Rails says the packaged Debian and Ubuntu policies do not already deny the involved coders.
The shipped policy applies through MiniMagick. Applications that replace its environment or shell configuration may miss it. GraphicsMagick does not read ImageMagick policies. Check these integrations directly, including deployments using custom image processing.
Timeline
- 2026-11-04
Rails published GHSA-f3w6-w445-fwh9 and fixed Active Storage releases 8.1.4.1 and 8.0.5.2.
- 2026-11-04
NVD published the CVE-2026-122006 record.
- 2026-11-12
NVD last modified its CVE-2026-126082 record, which was marked rejected as a duplicate when checked on November 13.
What to do
-
Upgrade Active Storage and verify the running version
Install activestorage 8.0.5.2 or 8.1.4.1 for the applicable branch. Check the resolved gem and running application after deployment; do not rely only on the lockfile change.
-
Check image processing and policy delivery
Confirm whether untrusted uploads use ImageMagick through :mini_magick. Rails requires mini_magick 5.1 or later for the shipped policy. Check application startup and verify custom MiniMagick configuration does not bypass the policy.
-
Handle Disk service secrets
For affected deployments storing attachments with Disk, follow Rails guidance to rotate secret_key_base and every secret readable by the application process. Replace, rather than retain, exposed values as fallbacks.
-
Review uploads and server activity
Brandefense recommends reviewing untrusted attachment submissions, unexpected file changes, and application access to secrets. Treat findings as investigation leads; the saved counts do not verify an attack.
-
Plan for ImageMagick compatibility
If the application renders PostScript or PDF through ImageMagick, test the fixed policy. Rails says required Ghostscript coders and delegates may need explicit allowance in the host policy.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-122006 in Brandefense Atlas
The Atlas record of CVE-2026-122006: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
What is CVE-2026-122006?
It is the active CVE record for an Active Storage ImageMagick vulnerability. Rails says untrusted uploads may permit arbitrary file writes and, with Disk storage, reads of application-accessible files.
Is CVE-2026-126082 a separate Rails flaw?
The Rails advisory displays that identifier, but NVD rejected it as a duplicate. NVD's CVE-2026-122006 record references the same Rails advisory, so this profile covers one issue.
Which Active Storage releases fix the issue?
Rails lists 8.0.5.2 and 8.1.4.1 as fixed releases. Confirm the resolved activestorage gem version and running deployment after updating.
Does every Rails application need secret rotation?
Rails specifically directs Disk service deployments to rotate secret_key_base and all secrets readable by the application process. Investigate exposure before deciding the response for other storage configurations.
Is CVE-2026-122006 known to be exploited?
The saved sources do not establish active exploitation. CISA KEV catalog version 2026.11.10 did not list either identifier. Dark chat posts and a repository name are interest signals, not incident evidence.
Sources
- Possible arbitrary file write and read in Active Storage image analysisRuby on Rails
- CVE-2026-122006 DetailNational Vulnerability Database
- CVE-2026-126082 DetailNational Vulnerability Database
- Known Exploited Vulnerabilities CatalogCybersecurity and Infrastructure Security Agency