Is carrierwave 3.1 vulnerable?

RubyGems · 5 releases from 3.1.0 to 3.1.4 · latest carrierwave is 3.1.4 · checked 18 Nov 2026

No known advisories in the last release

carrierwave 3.1.4, the last 3.1 release, has no known advisories. 1 advisory affects earlier 3.1.x releases, so update to 3.1.4.

Update within 3.1:bundle update --conservative carrierwave # Gemfile: '>= 3.1.4'

Is your project on an affected carrierwave?

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

Fixed within 3.1.x, affecting earlier releases

  • MediumCVE-2026-44587GHSA-7g26-2qgj-chfg27 May 2026

    CarrierWave has a denylisted_content_type bypass via Unescaped Regex Metacharacters

    Affected
    >=3.0.0.beta <3.1.3 · <2.2.7
    Fixed in
    2.2.7, 3.1.3

Every carrierwave 3.1.x release

Affected: 3.1.0 to 3.1.2. 3.1.3 and later are not affected.

VersionKnown advisories
carrierwave 3.1.4None
carrierwave 3.1.3None
carrierwave 3.1.2CVE-2026-44587
carrierwave 3.1.1CVE-2026-44587
carrierwave 3.1.0CVE-2026-44587

Which of your client projects are still on carrierwave 3.1?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact carrierwave version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other carrierwave versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the RubyGems registry. Refreshed daily.