Vulnerabilities in pkg:gem/pitchfork

PACKAGE
Advisory Identifier: GHSA-pfqj-w6r6-g86v
Share
Advisory Summary

CVE-2025-30221 is a MODERATE (CVSS 4.3) pitchfork http request/response splitting vulnerability vulnerability (CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')) affecting Pitchfork libraries in the RubyGems ecosystem. The issue involves pitchfork http request/response splitting vulnerability. Remediation is available by upgrading affected packages to version 0.11.0.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:gem/pitchfork

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:gem/pitchfork. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-pfqj-w6r6-g86v CVE-2025-30221 MODERATE Pitchfork HTTP Request/Response Splitting vulnerability

CVE-2025-30221 at a Glance

CVE Identifier CVE-2025-30221
GHSA Identifier GHSA-pfqj-w6r6-g86v
Severity MODERATE
CVSS v3.1 Base Score 4.3
CWE Classification CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')
Affected Product Pitchfork
Package Ecosystem RubyGems
Published Date
Last Updated

Security Impact

CVSS: 4.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2025-30221

To remediate this vulnerability, upgrade all affected Pitchfork dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

pitchfork fixed: 0.11.0 
Upgrade pitchfork to 0.11.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for pitchfork

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-30221, inspect your project dependencies for Pitchfork:

inspect dependencies for pitchfork

Analyze the terminal output to locate any version of Pitchfork in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.11.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting'), where the product receives data from an http agent/component (e.g., web server, proxy, browser, etc.), but it does not neutralize or incorrectly neutralizes cr and lf characters before the data is included in outgoing http headers. In Pitchfork, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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.

CVE-2025-30221 Affected Pitchfork Versions

1 component(s)
Fixed Versions:
0.11.0
Product / Package Ecosystem Affected Versions Fixed Version
pitchfork
gem/pitchfork
RubyGems
< 0.11.0
0.11.0

References

GitHub Advisory / Wiki ADVISORY
https://github.com/Shopify/pitchfork/security/advisories/GHSA-pfqj-w6r6-g86v
NVD — CVE-2025-30221 NVD
https://nvd.nist.gov/vuln/detail/CVE-2025-30221
Security Fix Commit FIX COMMIT
https://github.com/Shopify/pitchfork/commit/17ed9b61bf9f58957065f7405b66102daf86bf55
Pitchfork Source Repository REPOSITORY
https://github.com/Shopify/pitchfork
Pitchfork Source Repository REPOSITORY
https://github.com/rubysec/ruby-advisory-db/blob/master/gems/pitchfork/CVE-2025-30221.yml

Frequently Asked Questions

What is CVE-2025-30221?
CVE-2025-30221 is a security vulnerability in Pitchfork involving Pitchfork HTTP Request/Response Splitting vulnerability under CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting').
Which Pitchfork versions are affected?
Affected versions include releases prior to 0.11.0 across affected packages: pitchfork.
What version fixes CVE-2025-30221?
Upgrading to 0.11.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is pitchfork affected?
Yes, pitchfork is affected in releases prior to 0.11.0. Upgrade your dependency to 0.11.0 or later.
What is the CVSS score of CVE-2025-30221?
CVE-2025-30221 has a CVSS v3.1 base score of 4.3 (MODERATE) with vector string CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N.
What CWE is associated with CVE-2025-30221?
CVE-2025-30221 is classified under CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') (The product receives data from an HTTP agent/component (e.g., web server, proxy, browser, etc.), but it does not neutralize or incorrectly neutralizes CR and LF characters before the data is included in outgoing HTTP headers.).
How can I check RubyGems dependencies for CVE-2025-30221?
Run the dependency tree command: 'inspect dependencies for pitchfork'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-pfqj-w6r6-g86v",
  "modified" : "2025-03-28T16:12:43Z",
  "published" : "2025-03-27T18:01:18Z",
  "aliases" : [ "CVE-2025-30221" ],
  "summary" : "Pitchfork HTTP Request/Response Splitting vulnerability",
  "details" : "### Impact\nHTTP Response Header Injection in Pitchfork Versions < 0.11.0 when used in conjunction with Rack 3\n\n### Patches\nThe issue was fixed in Pitchfork release 0.11.0\n\n### Workarounds\nThere are no known work arounds. Users must upgrade.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "RubyGems",
      "name" : "pitchfork"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.11.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/Shopify/pitchfork/security/advisories/GHSA-pfqj-w6r6-g86v"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-30221"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/Shopify/pitchfork/commit/17ed9b61bf9f58957065f7405b66102daf86bf55"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/Shopify/pitchfork"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/rubysec/ruby-advisory-db/blob/master/gems/pitchfork/CVE-2025-30221.yml"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-113" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-03-27T18:01:18Z",
    "nvd_published_at" : "2025-03-27T15:16:02Z"
  }
}