PRIMARY-SOURCE REVIEW · 2026-11-13T18:25:00+09:00

Active Storage: attachment alone can reach arbitrary file operations

Applications accepting untrusted uploads with mini_magick processing and a policy that permits the relevant ImageMagick coders may allow arbitrary file writes merely by attaching an image. Disk service additionally exposes files readable by the process. Preview generation and an explicit analyze call are not prerequisites.

What to check

Update activestorage to 8.0.5.2 / 8.1.4.1, check mini_magick >= 5.1 and the effective policy. Check that overrides such as MiniMagick.cli_env do not bypass it. For potentially exposed Disk service secrets, rotate/revoke secret_key_base, the master key and external tokens; do not retain exposed secrets as fallbacks.

A first fixed version is listed only when the advisory provides one. Advisory counts are not incident counts.

Affected and fixed versions by advisory (1)

GHSA-f3w6-w445-fwh9

Active Storage: Possible arbitrary file write and read in image analysis

  • activestorage (rubygems): affected >= 8.1.0.beta1, < 8.1.4.1 → fixed 8.1.4.1
  • activestorage (rubygems): affected < 8.0.5.2 → fixed 8.0.5.2

Primary sources

GitHub reviewed advisory API — saved publication window / Rails maintainer advisory / JVN ImageMagick notice

Related topics

Rucio: SSH challenges accepted as authentication tokens enable administrator impersonation · Aspire: an unauthenticated NotFound route is not fixed by a runtime update · Hono: mount and router path differences can bypass authentication middleware · pgEdge RAG: ordinary concurrent queries can mix results across tenants · ScreenConnect: separate technician-client protection from compromise remediation · Air Terminal 6: OS command injection requires management login · KUSANAGI: the 11/12 revision clarifies Nginx redirect scope