How severe is GHSA-pfqj-w6r6-g86v?

GHSA-pfqj-w6r6-g86v has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-pfqj-w6r6-g86v?

GHSA-pfqj-w6r6-g86v affects the following packages: pitchfork (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-pfqj-w6r6-g86v?

Update pitchfork to 0.11.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pfqj-w6r6-g86v is resolved across your whole dependency graph.

How do I detect GHSA-pfqj-w6r6-g86v in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pitchfork, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-pfqj-w6r6-g86v if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-pfqj-w6r6-g86v actively exploited in the wild?

No public exploit code has been indexed for GHSA-pfqj-w6r6-g86v yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-pfqj-w6r6-g86v?

GHSA-pfqj-w6r6-g86v has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 22th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-pfqj-w6r6-g86v?

GHSA-pfqj-w6r6-g86v is classified as CWE-113 (CWE-113). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-pfqj-w6r6-g86v published, and has it been updated?

GHSA-pfqj-w6r6-g86v was published on March 27, 2025 and was last updated on March 28, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💎

💎 RubyGems

Not in CISA KEV

MEDIUM severity

Pitchfork HTTP Request/Response Splitting vulnerabilityGHSA-pfqj-w6r6-g86v

MEDIUMFix: Shopify/pitchfork@17ed9b6

GHSA-pfqj-w6r6-g86v is a medium-severity (CVSS 4.3) CWE-113 vulnerability in pitchfork. A fix is available for pitchfork — see the affected versions and patch details below.

Also known asCVE-2025-30221

Published

Mar 27, 2025

Updated

Mar 28, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-pfqj-w6r6-g86v.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs22th percentile — riskier than 22% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

💎pitchfork

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

Pitchfork is a preforking HTTP server for Rack applications. Versions prior to 0.11.0 are vulnerable to HTTP Response Header Injection when used in conjunction with Rack 3. The issue was fixed in Pitchfork release 0.11.0. No known workarounds are available.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`pitchfork`	all versions	0.11.0`bundle update pitchfork --conservative`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pitchfork, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pitchfork to 0.11.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pfqj-w6r6-g86v is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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