Security Digest · Vulnerability record

CVE-2026-122006: Active Storage: Possible arbitrary file write and read in image analysis

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 secretkeybase) because the ImageMagick analyzer runs when a file is attached, and there is not an ImageMagick security policy to block unintended…

CVSS 9.8 Critical EPSS 0.7% · p55

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
  • EPSS 0.7%, percentile 55: FIRST’s model estimates a 0.7% chance of exploitation activity in the next 30 days, higher than 55% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
  • Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
  • Only applies if your dependency tree includes activestorage (RubyGems) >= 8.1.0.beta1, < 8.1.4.1, fixed in 8.1.4.1; activestorage (RubyGems) < 8.0.5.2, fixed in 8.0.5.2. Check your lockfile, including transitive dependencies.

What it is

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 secretkeybase) because the ImageMagick analyzer runs when a file is attached, and there is not an ImageMagick security policy to block unintended functionality.

From the GitHub advisory

Impact A Rails application that processes attachments with ImageMagick may allow an unauthenticated attacker to write arbitrary files on the server and, when attachments are stored with the Disk service, to read arbitrary files readable by the application process. Those files typically include secretkeybase and credentials for external systems, which may in turn allow escalation to remote code execution or lateral movement to those systems.

Details ImageMagick selects a coder from the content of the file it is given, and some coders act on files named inside the image rather than on the image itself. Active Storage constrained none of ImageMagick's coders, and the ImageMagick analyzer runs when a file is attached, so an attacker who can upload a crafted file may be able to invoke one. Attaching the upload is sufficient; no variant, preview, or analyze call is required. One specific attack chain has been reported to us, but we do not assume it is the only one that exists.

The fixed versions ship an ImageMagick security policy and prepend its directory to MAGICKCONFIGUREPATH through MiniMagick.clienv, so every ImageMagick process that MiniMagick spawns applies it. The policy denies the MSL scripting coder, the coders that read or delete files other than the image, fetch remote or local references, or display to a screen, every coder backed by Ghostscript together with the gs delegate, and @filename indirection. ImageMagick applies every policy.xml on its search path, so the shipped policy adds to the host's policy rather than replacing it. The policy applies to every ImageMagick command that MiniMagick runs, not only those of Active Storage. See the activestorage CHANGELOG and "ImageMagick Security Policy" in the Active Storage guide.

Affected applications An application is affected if it meets all of these requirements: - Uses ImageMagick for Active Storage image processing. This is config.activestorage.variantprocessor = :minimagick, which is the default for applications on loaddefaults 6.1 or earlier. - Runs ImageMagick under a security policy that does not already deny the coders involved. The policies that Debian and Ubuntu package do not. - Allows file uploads from untrusted users.

Mitigation - Upgrade to a fixed version of activestorage. - An application whose variant processor is :minimagick…

Weakness type: CWE-1188.

Product: activestorage (RubyGems) · Assigned by: mitre · Published: 2026-11-04

Affected and fixed versions

EcosystemPackageVulnerableFirst fixed
RubyGemsactivestorage>= 8.1.0.beta1, < 8.1.4.18.1.4.1
RubyGemsactivestorage< 8.0.5.28.0.5.2
VendorProductAffected versions (per CVE record)
rubyonrailsActive Storage< 8.0.5.2, 8.1 < 8.1.4.1

Severity scores

Scored byCVSSScoreVector
mitre3.19.8 CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub3.19.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • Attack vector: network (remotely reachable)
  • Attack complexity: low
  • Privileges required: none (no login)
  • User interaction: none
  • Scope: unchanged

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
  • CISA SSVC assessment: exploitation none, automatable yes, technical impact total.
  • FIRST EPSS (model of 2026-11-21): 0.73% probability of exploitation activity in the next 30 days; percentile 55.

Timeline

  • — CVE record published by mitre
  • — CVE record last updated
  • — GitHub-reviewed advisory GHSA-f3w6-w445-fwh9 published (critical)

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

  1. GitHub Advisory GHSA-f3w6-w445-fwh9 github.com
  2. CVE.org record CVE-2026-122006 cve.org
  3. NVD entry CVE-2026-122006 nvd.nist.gov

Other references from the CVE record and advisory

  1. github.com github.com
  2. github.com github.com
  3. github.com github.com
  4. github.com github.com
  5. github.com github.com
  6. github.com github.com
  7. nvd.nist.gov nvd.nist.gov
  8. github.com github.com
  9. github.com github.com
  10. github.com github.com

Critical RubyGems advisories · Today’s Security Digest