How severe is GHSA-785g-282q-pwvx?

No CVSS score has been assigned to GHSA-785g-282q-pwvx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-785g-282q-pwvx?

GHSA-785g-282q-pwvx affects the following packages: rack-cors (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-785g-282q-pwvx?

Update rack-cors to 2.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-785g-282q-pwvx is resolved across your whole dependency graph.

How do I detect GHSA-785g-282q-pwvx in my RubyGems dependencies?

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

How do I mitigate GHSA-785g-282q-pwvx if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-785g-282q-pwvx actively exploited in the wild?

No public exploit code has been indexed for GHSA-785g-282q-pwvx 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-785g-282q-pwvx?

GHSA-785g-282q-pwvx has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 56th 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-785g-282q-pwvx?

GHSA-785g-282q-pwvx is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-785g-282q-pwvx published, and has it been updated?

GHSA-785g-282q-pwvx was published on February 26, 2024 and was last updated on March 4, 2024. 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

Rack CORS Middleware has Insecure File PermissionsGHSA-785g-282q-pwvx

GHSA-785g-282q-pwvx is a Information Exposure vulnerability in rack-cors. A fix is available for rack-cors — see the affected versions and patch details below.

Also known asCVE-2024-27456

Published

Feb 26, 2024

Updated

Mar 4, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 11, 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-785g-282q-pwvx.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs56th percentile — riskier than 56% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

💎rack-cors

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

rack-cors (aka Rack CORS Middleware) 2.0.1 has 0666 permissions for the .rb files.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`rack-cors`	≥ 2.0.1&&< 2.0.2	2.0.2`bundle update rack-cors --conservative`

Affected Products

1 product · 1 configurations

Application

rack cors middlewarerylabs

1 version

2.0.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rack-cors, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update rack-cors to 2.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-785g-282q-pwvx is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.