CVE-2025-30221 — Vulnerability in pitchfork — CVE Details
Pitchfork HTTP Request/Response Splitting vulnerability
Summary
Advisory Timeline
- First published March 27, 2025 (564 days ago).
- Last revised March 28, 2025 — 1 day after initial publication.
Remediation
Upgrade to the fixed version using your package manager.
gem install pitchfork -v 0.11.0
After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.
Affected Packages (1)
Affects 1 ecosystem: rubygems (1).
| Package | Ecosystem | Affected | Fixed In |
|---|---|---|---|
| pitchfork | rubygems | 0.1.0, 0.1.1, 0.1.2, 0.10.0 (+9 more) | 0.11.0 |
Vulnerability Classification
Common Weakness Enumeration (CWE) identifiers for this vulnerability type.
- CWE-113
CVSS Score Breakdown
What the CVSS (Common Vulnerability Scoring System) 4.3 score means for each attack dimension.
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
References
- https://github.com/Shopify/pitchfork/security/advisories/GHSA-pfqj-w6r6-g86vWEB
- https://nvd.nist.gov/vuln/detail/CVE-2025-30221ADVISORY
- https://github.com/Shopify/pitchfork/commit/17ed9b61bf9f58957065f7405b66102daf86bf55WEB
- https://github.com/Shopify/pitchforkPACKAGE
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/pitchfork/CVE-2025-30221.ymlWEB
Frequently Asked Questions
- What is CVE-2025-30221?
- Pitchfork HTTP Request/Response Splitting vulnerability This vulnerability has been assigned a severity rating of MEDIUM (CVSS score: 4.3/10).
- How do I check if my project is affected by CVE-2025-30221?
- CVE-2025-30221 affects pitchfork. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2025-30221 and 200,000+ other known vulnerabilities.
Severity & Exploitability
Exploitation requires specific conditions or has limited impact. Remediate within weeks.
Also Known As
Related CVEs
- CVE-2026-107715MEDIUM
Mechanize sends credential headers to another host after an HTTP redirect
- CVE-2026-107399MEDIUM
Mechanize sends credential headers to another origin after a meta refresh
Check if you're affected
Scan your dependencies to see if this vulnerability affects your projects.
Scan Your Dependencies