CriticalGHSA-r4mg-4433-c7g3CVE-2025-24293

Active Storage allowed transformation methods that were potentially unsafe

Published 14 Aug 2025 · Updated 31 Jan 2026

Is your project on an affected activestorage?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=8.0 <8.0.2.1
Fixed in
8.0.2.1
Update to the fixed version for your release line, for example:bundle update --conservative activestorage # Gemfile: '>= 8.0.2.1'
Affected
>=7.2 <7.2.2.2
Fixed in
7.2.2.2
Update to the fixed version for your release line, for example:bundle update --conservative activestorage # Gemfile: '>= 7.2.2.2'
Affected
>=5.2.0 <7.1.5.2
Fixed in
7.1.5.2
Update to the fixed version for your release line, for example:bundle update --conservative activestorage # Gemfile: '>= 7.1.5.2'

Details

Active Storage attempts to prevent the use of potentially unsafe image transformation methods and parameters by default.

The default allowed list contains three methods allowing for the circumvention of the safe defaults which enables potential command injection vulnerabilities in cases where arbitrary user supplied input is accepted as valid transformation methods or parameters.

This has been assigned the CVE identifier CVE-2025-24293.

Versions Affected: >= 5.2.0 Not affected: < 5.2.0 Fixed Versions: 7.1.5.2, 7.2.2.2, 8.0.2.1

Impact ------ This vulnerability impacts applications that use Active Storage with the image_processing processing gem in addition to mini_magick as the image processor.

Vulnerable code will look something similar to this:

<%= image_tag blob.variant(params[:t] => params[:v]) %>

Where the transformation method or its arguments are untrusted arbitrary input.

All users running an affected release should either upgrade or use one of the workarounds immediately.

Releases -------- The fixed releases are available at the normal locations.

Workarounds ----------- Consuming user supplied input for image transformation methods or their parameters is unsupported behavior and should be considered dangerous.

Strict validation of user supplied methods and parameters should be performed as well as having a strong ImageMagick security policy deployed.

Credits -------

Thank you lio346 from Unit 515 of OPSWAT for reporting this!

Is GHSA-r4mg-4433-c7g3 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected activestorage, and gives you the command that fixes it.

More advisories for activestorage

  • CriticalCVE-2026-122006Active Storage: Possible arbitrary file write and read in image analysis · 12 Nov 2026
  • MediumCVE-2026-126084Active Storage: Unsigned Content-Type in GCS direct uploads with cache_control · 12 Nov 2026
  • LowCVE-2026-126188Active Storage: Possible local file disclosure in video previews and analysis · 12 Nov 2026
  • HighCVE-2026-126186Active Storage: Possible arbitrary file read and remote code execution in video previews, analysis and image processing · 10 Nov 2026
  • MediumCVE-2026-126085Active Storage: Possible circumvention of file size limits in Active Storage direct uploads to Google Cloud Storage · 10 Nov 2026
  • MediumCVE-2026-126074Active Storage: Possible DoS vulnerability in Active Storage filename handling · 10 Nov 2026
All 18 advisories for activestorage

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.