Learn/railsffmpegvideosecurity

A Critical Rails Flaw Is a Reason to Keep Household Video at Home

A critical Rails flaw in Active Storage can write server files from an image upload. A second bug lets a filename choose an FFmpeg decoder. Keep the video at home.

Signed by M·
Dusk brick yard where a dark frame on the green plate holds the bright orb, smaller orbs sit on brick posts, and golden threads link the posts to the houses
What should a household do about the critical Rails flaw?

The critical Rails flaw is an Active Storage upload bug disclosed on November 4, 2026. ImageMagick can write files on the server, and a second bug in the same releases lets a filename choose an FFmpeg decoder. This site runs neither. Household video should stay on a computer that does not hand the file to those tools.

A critical Rails flaw disclosed on November 4, 2026 is a file-upload bug in Active Storage, the part of Rails that stores attachments. The Hacker News report is the writeup most people will find first. The project's own notes are the two advisories: image analysis that can write files, and a filename handed to FFmpeg. This page is the house reading of those notes. It is not a patch guide, and it does not repeat an upload that reaches the bug.

The critical Rails flaw matters here because the file in the story is a picture or a video. That is the archive a household already has. Remade With Rust is the family writing a reader for that archive in Rust. The computer that should open the file is Home on MATA.

What the critical Rails flaw actually reaches

Rails rates the ImageMagick issue 9.8. It is GHSA-f3w6-w445-fwh9. As of this writing, The Hacker News reports it does not yet have a CVE. An application is in scope only when three things are true. It uses ImageMagick for Active Storage, which is the :mini_magick setting and the default for apps on load_defaults 6.1 or earlier. Its ImageMagick policy does not already deny the coders involved, and the policies Debian and Ubuntu ship do not. It accepts uploads from people the app does not trust. Fixed versions are Rails 8.1.4.1 and 8.0.5.2. Every Active Storage version before 8.0.5.2 is affected, and 8.1 versions before 8.1.4.1. Release lines older than 8.0 are unsupported, so they do not get a fixed gem. A critical Rails flaw on one of those lines stays open. The advisory does not say the flaw has been exploited. RyotaK of GMO Flatt Security reported it.

An analyzer that runs when the file is attached

ImageMagick picks a coder from the content of the file. Some coders act on other files, not on the picture. Active Storage did not limit which coders an upload could use. The analyzer runs when a file is attached. The app does not have to make a resized copy, a preview, or call analyze. One reported chain reached a scripting coder. Rails says it does not assume that chain is the only one. On apps that store attachments with the Disk service, the same class of bug can also read files the app process can read. Rails names secret_key_base and the credentials for other systems. Reading those can become code execution on the server, or a step into those other systems. A critical Rails flaw of this shape is an upload that never had to look like a finished image on a page.

The filename FFmpeg was given

The same releases fix a second Active Storage issue, GHSA-v924-7rp8-4mxh, rated 8.8. Beside the critical Rails flaw, this is the bug that names FFmpeg. Active Storage wrote the upload to a temporary file whose name kept the uploaded extension, then passed that path to ffprobe, to ffmpeg, and to ImageMagick. Those tools can pick a decoder from the extension when the content does not name its own format. An upload's filename and its declared type were enough to choose the decoder. One path needs an FFmpeg build that common Linux packages and Homebrew do not ship. The advisory says that path can disclose files the app can read, or run code in the FFmpeg process. Other decoders chosen from the extension may be reachable without that build. This issue asks for someone who can already upload, which the score treats as a low privilege. It is not the fully open bar of the 9.8 issue. The Hacker News account says the two releases fix 21 security issues in total, and that Rails 8.0 receives security fixes only until November 7, 2026.

Why that validates our FFmpeg alternative

The second advisory is the sentence this house has been writing toward. A web framework kept a stranger's filename and asked the FFmpeg program to understand the file. The critical Rails flaw validates our FFmpeg alternative by showing the job a household reader must not do. Our FFmpeg alternative is that reader. It opens a local recording through its own demuxers. It does not hand that recording to the FFmpeg binary the advisory is about. That is the validation. It is not a claim that the library is the Rails patch, and it is not a crates.io release of the tree measured in October.

A file the house already has

The trust boundary is the difference. Rails Active Storage analyzes an upload when the file is attached, and it does that by default for video and audio. The household path is the opposite. A camera or a microphone has already written a file, and a computer in the house opens it. Our FFmpeg alternative stopped reading the whole file is the measurement of that open. On the formats just rewritten, a local file no longer has to be copied into RAM before the streams can be named, and the bytes out of a well-formed file stayed the same. Garbage inputs in that work are required to finish without a panic. None of that closes GHSA-v924-7rp8-4mxh inside a Ruby app. A Rails app still has to upgrade. An output name the operator chose, such as a WebP file, can still select an output codec. That is the operator's destination. It is not a stranger choosing a decoder by the name of an upload.

What a remake does not close

Writing the reader in Rust removes the step where a web process shells the family archive out to FFmpeg. The critical Rails flaw remains a Rails upgrade. It is not a crate you swap in. A logic bug in Rust still ships as a logic bug. The ESP32 does not run these demuxers. The camera page in rusty_esp_video is a stream on the local network, and it drops frames instead of buffering them on the board. The home computer's media view is not wired to that stream yet. Those limits are written on the MATA Home integration. The language of the reader is not a promise that a hostile file is harmless. It is a statement about who opens a file the house already made, and which program they ask.

Why personal video and pictures have to stay home

Pictures and recordings are the payload because photo apps and video uploads run them through a media tool. The critical Rails flaw is one week of that pattern. In July, Rails fixed a different Active Storage flaw, CVE-2026-66066, on the libvips path. The Hacker News report says apps using ImageMagick were not on that path, and that they can be on this one. ImageMagick's coder list and FFmpeg's decoder list are not finished. Each added coder is another way a file is not only pixels. Rails published one chain and said not to assume it is the only one. That is how this class grows: the next coder, the next extension, the next library a framework shells out to. A household that waits for each advisory is always one library behind.

The archive grows on the same curve

A household's video grows whether or not Rails does. More cameras, longer recordings, and more apps that ask for the clip. The exposure is those two curves multiplied. A porch recording that used to sit on a disk becomes an attachment a framework wants to inspect on the way in. Treating the critical Rails flaw as a single patch misses that curve. Locking the archive down means refusing the hop. The file stays on the computer that already has it. Smart home access on your home computer is the series for that job. When a home camera company watches your house is the older warning: once the video has left, the household is no longer the one holding it. The pile of personal video will keep growing. The number of tools willing to interpret a stranger's file will keep growing with it.

What this origin runs instead

dldeploy.com does not run Rails, Active Storage, ImageMagick, or FFmpeg against an upload. The pages are files a Rust program already wrote. nginx serves them. A request for this note does not attach a picture, so the critical Rails flaw has no object here. Operators who do run Rails should move to 8.1.4.1 or 8.0.5.2. If the Disk service could already have been read, they should change the secrets that process could see. The advisory's temporary step for ImageMagick does not cover the FFmpeg issue. The See vision is the camera half of the house path. The Own vision is the key half. The Learn index is the list of what has actually been measured. The program Rails handed the upload to remains FFmpeg. Our FFmpeg alternative is the attempt to stop asking that program to open the family's files.

FAQ

Quick answers for builders evaluating this technology.

Which Rails versions fix the critical Rails flaw?

Rails 8.1.4.1 and 8.0.5.2. Active Storage before 8.0.5.2 is affected, as are 8.1 versions before 8.1.4.1. Lines older than 8.0 are unsupported and do not get a fixed release.

Does dldeploy.com run the code in the critical Rails flaw?

No. This site is prerendered files served by nginx. There is no Rails app, no Active Storage, and no upload path that calls ImageMagick or FFmpeg.

Does our FFmpeg alternative replace FFmpeg inside Rails?

No. It is a local reader for a file the household already has. It is not a drop-in for Active Storage, and the tree measured in October is not a crates.io release. A Rails app still has to upgrade.

Did Rails say the critical Rails flaw was already exploited?

No. The advisory says one attack chain was reported and that they do not assume it is the only one. It does not say the flaw has been used in the wild.

Why will flaws like the critical Rails flaw keep growing?

ImageMagick and FFmpeg keep adding coders, and frameworks keep handing them uploads. July was a libvips Active Storage bug. November is ImageMagick and a filename passed to FFmpeg. Household video libraries grow on the same years.