On this page (7 sections)
A GitHub advisory describes a critical weakness in the Active Storage component of Ruby on Rails: when ImageMagick processes an attachment, the analyzer can allow server file reads and writes, with reading secret_key_base given as an example. The advisory, GHSA-wgv4-95jc-33jm, was withdrawn on Nov 12, 2026 as a duplicate of another entry, so treat it as a pointer rather than the final word.
If you run a Rails app that accepts uploads and uses ImageMagick for image handling, this is worth a quick review today. Only one source is available for this story, and it contains some inconsistencies that are spelled out below.
What the advisory says
According to the GitHub advisory, the original description reads that the activestorage gem, when ImageMagick attachment processing occurs, can allow server read and write operations, for example reading secret_key_base. The stated cause is that the ImageMagick analyzer runs when a file is attached, and no ImageMagick security policy exists to block unintended functionality.
The advisory classifies the weakness as CWE-1188, Initialization of a Resource with an Insecure Default. In plain terms, the risky behavior is not a coding slip in one function but a default setup that leaves ImageMagick's powerful features switched on unless an administrator restricts them.
Why the withdrawal does not mean the risk is gone
GitHub withdrew this entry because it duplicates GHSA-f3w6-w445-fwh9, and says the link is kept only to preserve external references. A withdrawal for duplication is not a statement that the issue is invalid. The advisory page does not reproduce the content of the other entry, so check it directly for its own details.
The page also contradicts itself on versions. The affected field says versions below 8.0.5.2, the description says before 8.1.4.1, and the patched-versions field says None, while the references include release tags for both v8.0.5.2 and v8.1.4.1. The source does not explain this discrepancy. Check the duplicate advisory GHSA-f3w6-w445-fwh9 and the Rails release notes to confirm which versions are affected and which are fixed before relying on a version number.
Who is realistically exposed
The description ties the problem to ImageMagick attachment processing in Active Storage. Apps are most likely to be relevant if they:
- Use Rails with the activestorage gem and accept file uploads, especially from untrusted or anonymous users.
- Have ImageMagick installed on the server and used to analyze or transform images.
- Have no ImageMagick security policy configured on the host or container image.
- Run on an activestorage version older than the release tags referenced in the advisory.
The CVSS vector shows network attack, low complexity, no privileges and no user interaction. That describes the scoring assumption, not a confirmed attack on any real site. The secret_key_base example matters because that value protects signed and encrypted data in a Rails app, so its disclosure would have serious follow-on effects.
How to check your exposure
These read-only checks show which Active Storage version your app uses and whether ImageMagick is present. Run the first from your app directory and look for the activestorage line in the output.
bundle list | grep activestorageNext, check whether ImageMagick is installed on the host and which version. On ImageMagick 7 the command is magick, and on version 6 it is convert. A version line in the output means it is installed.
magick -version || convert -versionThen look at whether your app's image handling actually uses ImageMagick. This search lists lines in your configuration that mention the variant processor or Active Storage settings.
grep -rn "variant_processor\|active_storage" config/What to do now
- Read the duplicate advisory GHSA-f3w6-w445-fwh9 and the NVD entry for CVE-2026-122006, and note the affected and fixed versions they list.
- Check your activestorage version with the command above and compare it to the release tags referenced in the advisory, v8.0.5.2 and v8.1.4.1, once you have confirmed the correct fixed version.
- Upgrade Rails to the confirmed patched release on your line, test uploads and image variants, then deploy.
- If you cannot upgrade immediately, consider turning off ImageMagick-based analysis for untrusted uploads or restricting who can upload, after testing the impact on your app.
- Review the ImageMagick security policy on your servers and container images, since the advisory names its absence as the cause.
- If you suspect the vulnerable setup was exposed to untrusted uploads, consider rotating secret_key_base and other secrets, since the advisory names it as readable. Rotation signs users out and invalidates signed data, so plan for that.
- Review upload and application logs for unusual attachments or unexpected errors around image analysis.
For the ImageMagick policy itself, follow ImageMagick's own documentation and your distribution's guidance. The research gives no specific policy contents, so this article does not suggest any.
Detection and monitoring afterwards
Because the advisory describes file reads and writes on the server, watch for signs that go beyond the upload form: new or modified files outside upload directories, unexpected processes spawned by the app user, and unusual outbound connections. Keep dependency tooling such as bundler-audit or your CI's advisory checks running so duplicates and corrections like this one reach you.
An outside-in scan cannot see inside your app's gems or ImageMagick configuration, so version checks on the server remain essential. Our guide to what outside-in malware detection can and cannot see explains that limit, and the free malware scanner can help check public pages for signs of tampering.
Timeline
| Date | Event |
|---|---|
| Nov 4, 2026 | Published by the National Vulnerability Database and to the GitHub Advisory Database |
| Nov 12, 2026 | Reviewed by GitHub and withdrawn as a duplicate of GHSA-f3w6-w445-fwh9 |
| Nov 12, 2026 | Advisory page last updated |
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
