CVE-2025-30221: Pitchfork HTTP Request/Response Splitting vulnerability
Impact HTTP Response Header Injection in Pitchfork Versions < 0.11.0 when used in conjunction with Rack 3 Patches The issue was fixed in Pitchfork release 0.11.0 Workarounds There are no known work arounds. Users must upgrade.
Published Mar 27, 2025 · Updated Mar 28, 2025
Affected packages
pitchfork
- Ecosystem
- RubyGems
- Affected
- < 0.11.0
- Fixed in
- 0.11.0
- Check
bundle info pitchfork
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
HTTP Response Header Injection in Pitchfork Versions < 0.11.0 when used in conjunction with Rack 3
Patches
The issue was fixed in Pitchfork release 0.11.0
Workarounds
There are no known work arounds. Users must upgrade.
References
- https://github.com/Shopify/pitchfork/security/advisories/GHSA-pfqj-w6r6-g86v
- https://nvd.nist.gov/vuln/detail/CVE-2025-30221
- https://github.com/Shopify/pitchfork/commit/17ed9b61bf9f58957065f7405b66102daf86bf55
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/pitchfork/CVE-2025-30221.yml
- https://github.com/advisories/GHSA-pfqj-w6r6-g86v
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
