AEGLIX News
A critical vulnerability in Ruby on Rails Active Storage enables unauthenticated attackers to write arbitrary files on application servers through crafted SVG uploads processed by ImageMagick, according to a security advisory released by the Rails team. The flaw occurs when an uploaded SVG file reaches ImageMagick's MSL coder through the Active Storage analyzer, creating a path for remote file system manipulation without authentication.
The vulnerability affects every Active Storage version prior to 8.0.5.2 and all 8.1 versions before 8.1.4.1, while release series older than 8.0 remain unsupported and will not receive patches. Applications are only exposed when they use ImageMagick for Active Storage image processing, have ImageMagick security policies that do not block the involved coders, and accept uploads from untrusted users. Notably, apps using libvips instead of ImageMagick were not vulnerable to this attack path, as confirmed by a separate critical flaw fixed in July affecting libvips-based configurations.
Rails acknowledged that one attack chain was reported to the project but explicitly stated it does not assume this represents the only exploitation vector. The advisory does not confirm whether the vulnerability has been actively exploited in the wild. Applications relying on the :mini_magick backend additionally require mini_magick version 5.1 or later, otherwise they will raise an error at boot time, indicating a dependency-level mitigation requirement beyond the core Rails patch.
Fixed versions 8.0.5.2 and 8.1.4.1 are now available for supported release series. For applications storing attachments with the Disk service, Rails advises changing the secret_key_base and every other secret the application process can read, including the master key, credentials.yml.enc contents, storage and database credentials, and third-party tokens. This comprehensive credential rotation addresses potential exposure from arbitrary file write capabilities on the server filesystem.
Report prepared 2026-11-05 · Based on reporting from The Hacker News. Source publication date above; subsequent developments may not be reflected.