CVE-2025-24293
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · unedited# Active Storage allowed transformation methods potentially unsafe Active Storage attempts to prevent the use of potentially unsafe image transformation methods and parameters by default. The default allowed list contains three methods allow 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. 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. 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](https://imagemagick.org/script/security-policy.php) deployed. Credits ------- Thank you [lio346](https://hackerone.com/lio346) for reporting this!
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceActive Storage's default allowlist for image transformation methods contains entries that can be circumvented, enabling command injection when applications accept arbitrary user input for transformation methods or parameters. This affects only applications using both the image_processing gem and mini_magick as the image processor.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Active Storage is in useCheck your Rails application configuration (config/application.rb, Gemfile) for 'active_storage' in Gemfile or config.active_storage present in initializersAffected if Active Storage is not being used in the application
-
Verify image_processing gem is installedRun 'gem list image_processing' or check Gemfile.lock for the image_processing gemAffected if image_processing gem is not present in the project dependencies
-
Check if mini_magick is configured as the image processorInspect config/environments/development.rb (or other environment files) for config.active_storage.analyze = false and look for mini_magick usage in the codebase; also check Gemfile.lock to confirm mini_magick is installedAffected if mini_magick is not configured or is not being used as the image processor (e.g., using vips instead)
-
Identify if user input flows into transformation methodsSearch codebase for Active Storage variant calls that accept user-supplied parameters, such as: variant(resize: params[:resize]), variant(params[:transform]), or similar patterns using request/params in variant definitionsAffected if Application code passes untrusted user input directly to Active Storage variant transformation methods or parameters
Your environment is affected only if you use Active Storage with the image_processing gem and mini_magick, AND your application accepts arbitrary user input for transformation methods or parameters without strict allowlist validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to a patched Rails version that restricts the transformation method allowlist, and eliminate any patterns that pass user-supplied input directly to variant transformations.
Rails 7.1.x or later (with Active Storage fix)
- 1. Identify the Rails version currently in use by checking the Gemfile.lock or running `bundle exec rails --version`
- 2. Identify the Active Storage version by checking the Gemfile.lock for 'activesorage'
- 3. Upgrade to Rails 7.1.x or later which contains the fix for this vulnerability
- 4. Run `bundle update rails` or specify the new Rails version in Gemfile and run `bundle install`
- 5. Verify the upgrade by testing image variant generation with your Active Storage setup
- 6. If upgrading is not immediately possible, implement strict validation on any user-supplied transformation parameters before passing them to Active Storage variants
- 7. Additionally, configure ImageMagick security policies as a defense-in-depth measure
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24293 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-24293 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data