How severe is GHSA-8cgq-6mh2-7j6v?

No CVSS score has been assigned to GHSA-8cgq-6mh2-7j6v yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8cgq-6mh2-7j6v?

GHSA-8cgq-6mh2-7j6v affects the following packages: rack (RubyGems), rack (RubyGems), rack (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-8cgq-6mh2-7j6v?

Update rack to 2.2.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8cgq-6mh2-7j6v is resolved across your whole dependency graph.

How do I detect GHSA-8cgq-6mh2-7j6v in my RubyGems dependencies?

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

How do I mitigate GHSA-8cgq-6mh2-7j6v 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-8cgq-6mh2-7j6v actively exploited in the wild?

No public exploit code has been indexed for GHSA-8cgq-6mh2-7j6v 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-8cgq-6mh2-7j6v?

GHSA-8cgq-6mh2-7j6v has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 55th 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-8cgq-6mh2-7j6v?

GHSA-8cgq-6mh2-7j6v is classified as CWE-93 (CWE-93), CWE-117 (CWE-117). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-8cgq-6mh2-7j6v published, and has it been updated?

GHSA-8cgq-6mh2-7j6v was published on March 4, 2025 and was last updated on September 10, 2026. 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

Escape Sequence Injection vulnerability in Rack lead to Possible Log InjectionGHSA-8cgq-6mh2-7j6v

Fix: rack/rack@803aa22

GHSA-8cgq-6mh2-7j6v is a CWE-93 vulnerability in rack. A fix is available for rack — see the affected versions and patch details below.

Also known asCVE-2025-27111

Published

Mar 4, 2025

Updated

Sep 10, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
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-8cgq-6mh2-7j6v.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk

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

Real-World Exposure

3 pkgs affected

💎rack💎rack💎rack

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

Summary

Rack::Sendfile can be exploited by crafting input that includes newline characters to manipulate log entries.

Details

The Rack::Sendfile middleware logs unsanitized header values from the X-Sendfile-Type header. An attacker can exploit this by injecting escape sequences (such as newline characters) into the header, resulting in log injection.

Impact

This vulnerability can distort log files, obscure attack traces, and complicate security auditing.

Mitigation

Update to the latest version of Rack, or
Remove usage of Rack::Sendfile.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`rack`	all versions	2.2.12`bundle update rack --conservative`
💎RubyGems	`rack`	≥ 3.0&&< 3.0.13	3.0.13`bundle update rack --conservative`
💎RubyGems	`rack`	≥ 3.1&&< 3.1.11	3.1.11`bundle update rack --conservative`

Affected Products

1 product · 3 configurations

Application

rackrack

≥ 3.1.0 && < 3.1.11

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rack, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update rack to 2.2.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8cgq-6mh2-7j6v 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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Workaround published by Red Hat

To mitigate this vulnerability, remove usage of Rack::Sendfile.

Source: Red Hat security advisory for GHSA-8cgq-6mh2-7j6v (CC BY 4.0)

Frequently Asked Questions

## Summary `Rack::Sendfile` can be exploited by crafting input that includes newline characters to manipulate log entries. ## Details The `Rack::Sendfile` middleware logs unsanitized header values from the `X-Sendfile-Type` header. An attacker can exploit this by injecting escape sequences (such as newline characters) into the header, resulting in log injection. ## Impact This vulnerability can distort log files, obscure attack traces, and complicate security auditing. ## Mitigation - Update to the latest version of Rack, or - Remove usage of `Rack::Sendfile`.

O3 Security · Impact-Aware SCA

Is GHSA-8cgq-6mh2-7j6v in your dependencies?

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works