← Back
CVE-2026-44587
medium
CVSS 4.7
Cross-Site Scripting (XSS) in carrierwave (CVE-2026-44587)
Summary
cross-site scripting in carrierwave (CVE-2026-44587). Risk of unauthorized operations or information disclosure. Exploitable via ``Regexp.quote``. Mitigation: upgrade to `2.2.7` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-44587** has been found in carrierwave.
Attackers can target a specific entry point like ``Regexp.quote`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.7/10.
What to do: upgrade carrierwave to **2.2.7** or later.
If unsure, ask your IT team or search "carrierwave CVE-2026-44587" on the vendor's site.
CVE-2026-44587 (carrierwave) — CWE-79 / CVSS v3 4.7
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `Regexp.quote`
Patched: `2.2.7` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**Cross-site scripting (XSS)** (CWE-79) exists in carrierwave. Attackers reach the vulnerable code path via ``Regexp.quote`` without authentication.
📍 Affected scope
carrierwave — . Attack surface: `Regexp.quote`.
🔥 Severity
Severity: Medium (CVSS 4.7/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.2.7**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'carrierwave' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'carrierwave' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `carrierwave` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade carrierwave to 2.2.7ステージング環境で 2.2.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
rubygems
carrierwave
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.7"}]}]
References
- package https://github.com/carrierwaveuploader/carrierwave
- web https://github.com/carrierwaveuploader/carrierwave/security/advisories/GHSA-7g26-2qgj-chfg
- web https://github.com/advisories/GHSA-7g26-2qgj-chfg
- web https://github.com/rubysec/ruby-advisory-db/blob/master/gems/carrierwave/CVE-2026-44587.yml
- web https://www.cve.org/CVERecord?id=CVE-2026-44587
- web https://github.com/carrierwaveuploader/carrierwave/commit/21221cc6e260633f7da78c6133a88666a5529d27
- web https://github.com/carrierwaveuploader/carrierwave/commit/4c4a005775a436c5165df014dc9b1874c227d86c
- web https://nvd.nist.gov/vuln/detail/CVE-2026-44587