Plan this weekVulnerabilities

Rails fixes 21 security issues, one critical in Active Storage file uploads. Upgrade to 8.1.4.1 or 8.0.5.2

On 4 Nov 2026 the Rails team released 8.1.4.1 and 8.0.5.2 with fixes for 21 security issues. One is critical (arbitrary file write and read in Active Storage image analysis) and four are high, including file read and remote code execution in Active Storage video previews. The announcement does not mention attacks. Security support for Rails 8.0 ends on 7 Nov 2026. What to upgrade to and what to check.

Updated 13 Nov 2026: see what changed

How urgent

Plan this week

Who is affected

Rails apps on the 8.0 and 8.1 series that have not upgraded to 8.0.5.2 or 8.1.4.1. The announcement does not give exact ranges per issue; three issues are marked as affecting 8.1 only. The Active Storage issues matter most to apps that accept file uploads (images, video). Rails versions older than 8.0 are unsupported and get no fix

What to do

Upgrade to Rails 8.1.4.1 (or 8.0.5.2) as soon as you can, run your tests, and deploy. If you are on a version older than 8.0, plan the move to a supported series now: it receives no fix. Until you upgrade, review where your app accepts uploads and runs image or video analysis, and keep upload processing away from sensitive files and secrets

Published 5 Nov 2026 · Sources last checked 13 Nov 2026No. 48 / 87

Updates, follow-ups and corrections

  1. Update · 13 Nov 2026. The critical Active Storage flaw now has its full advisory (GHSA-f3w6-w445-fwh9, CVE-2026-122006, CVSS 9.8, no login needed), published on GitHub by the Rails team on 12 Nov. It says an attacker who can upload a crafted file to an app that processes images with ImageMagick may write files on the server and, with the Disk service, read files such as secret_key_base. It adds a mitigation (a policy.xml workaround and a secrets rotation) and a patch for each series. We did not find it in CISA's known exploited vulnerabilities catalog and the advisory mentions no attacks. We have not read the Rails announcement again or tested anything.
  2. Update · 5 Nov 2026. First version of the story, based on the Rails security announcement of 4 Nov 2026, read directly in the Rails forum. The announcement lists the issues but, in the page we read, gives no exploit details or exact affected ranges, and does not mention attacks. We have not checked each advisory.

We keep the original text. When something changes, when we follow a story, or when we get something wrong, we add a dated note here instead of editing silently.

What happened

On 4 November 2026 the Rails team released Rails 8.1.4.1 and 8.0.5.2, fixing 21 security issues. The maintainers say: "We strongly recommend upgrading as soon as possible."

By their own severity ratings, the 21 issues are 1 critical, 4 high, 13 medium and 3 low.

The ones to know first

  • Critical: arbitrary file write and read in Active Storage image analysis (GHSA-f3w6-w445-fwh9). Active Storage is the part of Rails that handles file uploads.
  • High: arbitrary file read and remote code executionRCE (remote code execution) A flaw that lets an attacker run their own code on your server or device from a distance. Tap again to open the glossary in Active Storage video previews, analysis and image processing (GHSA-v924-7rp8-4mxh).
  • High: a Strong Parameters bypass in Parameters#each_key, IP spoofing in RemoteIp through the Forwarded header (8.1 only), and a denial of service in safe_constantize.
  • The rest are mostly cross-site scripting in view helpers, denial of service, cache and session problems, and two issues in Google Cloud Storage direct uploads.

Update 13 November: the critical flaw in detail

The full advisory for the critical Active Storage flaw (CVE-2026-122006, CVSSCVSS score A number from 0 to 10 that rates how serious a flaw is in general. From 9.0 up it is called Critical. Tap again to open the glossary 9.8) is now public. What it says:

  • How it works: when you attach a file, Active Storage runs ImageMagick to analyze it, and ImageMagick picks how to read the file from its content. Some readers act on files named inside the image. An attacker who uploads a crafted file can make the server write arbitrary files and, if attachments are stored with the Disk service, read any file the app can read. The advisory says attaching the upload is enough: no variant, preview or analyze call is needed.
  • What is at stake: those files usually include secret_key_base and credentials for other systems, which can lead to code execution or to those systems.
  • Who is affected: all three must be true: you use ImageMagick for Active Storage images (variant_processor = :mini_magick, the default for load_defaults 6.1 or earlier), your ImageMagick policy does not already block the coders involved (the Debian and Ubuntu packages do not), and untrusted users can upload files. Affected: activestorage before 8.0.5.2, and 8.1 before 8.1.4.1.
  • The fix: the fixed versions ship an ImageMagick security policy. Apps using :mini_magick need mini_magick 5.1 or later, or they fail at boot. Apps that render PDF or PostScript through ImageMagick must re-allow the Ghostscript parts in their own policy.
  • Not upgrading yet: copy the rules of the shipped policy.xml into ImageMagick's system policy (at least deny the MSL coder, the Ghostscript coders and the gs delegate). PatchesPatch (security update) A fix released by the maker of a piece of software to close a flaw or a bug. Tap again to open the glossary for 8.0 and 8.1 are linked in the advisory.
  • SecretsSecret (API key, token, password) Any piece of text that proves to a service that you are allowed in, such as an API key, a database password or an access token. Tap again to open the glossary: if you use the Disk service, the advisory says to change secret_key_base and every secret the app can read, including the master key and what config/credentials.yml.enc holds. Do not keep an exposed secret as a fallback.
  • Attacks: the advisory mentions none and we did not find the flaw in CISA's known exploited vulnerabilitiesVulnerability A weakness in software, a setting or a process that an attacker could use to get in or do harm. Tap again to open the glossary catalog. It does say one attack chain was reported and others may exist.

Two steps are ours, not the advisory's: check variant_processor in your config and your ImageMagick version, and look at which upload fields accept files from people you do not know.

What we could and could not confirm

We read the announcement in the Rails forum. The page we read does not describe how each flaw is triggered, does not give exact affected ranges (apart from the three 8.1-only items), and does not say whether any of them has been used in attacks. We did not read each advisory and we did not test anything, so do not read "no attacks mentioned" as "no attacks".

Who is affected

Teams running Rails 8.0 or 8.1. Apps that accept uploads and analyze or preview them (profile photos, documents, video) should look at the Active Storage items first. The announcement says versions older than 8.0 are unsupported and recommends at least 8.0. It also says security support for the 8.0 series ends on 7 November 2026, so after that date 8.0 gets no more fixes.

What to do

  1. Upgrade to Rails 8.1.4.1 (or 8.0.5.2 if you must stay on 8.0), run your tests and deploy.
  2. If you are on a version older than 8.0, it receives no fix. Plan the move to a supported series now.
  3. Plan beyond 8.0. Since 8.0 security support ends on 7 November, put the upgrade to 8.1 on your list.
  4. Until you deploy, check where your app accepts uploads and runs image or video processing, and make sure that process cannot read secrets or sensitive files.
  5. Read the linked advisories for the items that touch your app (Active Storage, Strong Parameters, RemoteIp).

If you build with AI tools

Our advice, not from the announcement: AI assistants scaffold Rails apps with Active Storage uploads in a few lines and rarely mention updates. Ask yours which Rails version your app runs, whether it uses Active Storage analysis or previews, and to run the upgrade and your tests.

Watch the short video

The video loads from YouTube (privacy-enhanced mode) only when you press play.

Comments

No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.

    We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.

    Sources and verification

    We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.

    Spotted a mistake? Email [email protected] and we will correct it and note the change.

    Get the free runbooks

    One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

    Send me the runbooks