# carrierwave (RubyGems) vulnerabilities

5 known vulnerabilities (1 high, 4 medium), with the versions each affects and the releases that fix them.

## At a glance

- Latest release: not known (cve.now hasn't read this package's releases)
- Newest unaffected release: not known without release data
- Registry: https://rubygems.org/gems/carrierwave

## Advisories (5)

### [CVE-2026-44587](https://cve.now/CVE-2026-44587): CarrierWave has a denylisted\_content\_type bypass via Unescaped Regex Metacharacters

- Severity: Medium 4.7
- Published: Jun 16, 2026
- Affected: from 3.0.0.beta, fixed in 3.1.3; fixed in 2.2.7.

### [CVE-2024-29034](https://cve.now/CVE-2024-29034): CarrierWave's Content-Type allowlist bypass vulnerability which possibly leads to XSS remained

- Severity: Medium 6.8
- Published: Mar 24, 2024
- Affected: from 3.0.0, fixed in 3.0.7; fixed in 2.2.6.

### [CVE-2023-49090](https://cve.now/CVE-2023-49090): CarrierWave has a content-type allowlist bypass vulnerability, possibly leading to XSS

- Severity: Medium 6.8
- Published: Nov 29, 2023
- Affected: from 3.0.0, fixed in 3.0.5; fixed in 2.2.5.

### [CVE-2021-21305](https://cve.now/CVE-2021-21305): Code Injection vulnerability in CarrierWave

- Severity: High 7.4
- Published: Feb 8, 2021
- Affected: fixed in 1.3.2; from 2.0.0, fixed in 2.1.1.

### [CVE-2021-21288](https://cve.now/CVE-2021-21288): Server-side request forgery in CarrierWave

- Severity: Medium 4.3
- Published: Feb 8, 2021
- Affected: fixed in 1.3.2; from 2.0.0, fixed in 2.1.1.

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/packages/rubygems/carrierwave
Site guide for agents: https://cve.now/llms.txt
Uses NVD data; not endorsed by NVD.