GHSA-qp49-3pvw-x4m5 is a high-severity (CVSS 7.5) Path Traversal vulnerability in sinatra. A fix is available for sinatra — see the affected versions and patch details below.
sinatra does not validate expanded path matches
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-qp49-3pvw-x4m5 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
sinatraReal-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
Sinatra before 2.2.0 does not validate that the expanded path matches public_dir when serving static files.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 💎RubyGems | sinatra | all versions | 2.2.0bundle update sinatra --conservative |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sinatra, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update sinatra to 2.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qp49-3pvw-x4m5 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-qp49-3pvw-x4m5 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-qp49-3pvw-x4m5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Enterprise Linux 8 | pcs-0:0.10.12-6.el8_6.1 | RHSA-2022:4661 |
| Red Hat Enterprise Linux 8.1 Update Services for SAP Solutions | pcs-0:0.10.2-4.el8_1.2 | RHSA-2022:2255 |
| Red Hat Enterprise Linux 8.2 Extended Update Support | pcs-0:0.10.4-6.el8_2.2 | RHSA-2022:2253 |
| Red Hat Enterprise Linux 8.4 Extended Update Support | pcs-0:0.10.8-1.el8_4.1 | RHSA-2022:2256 |
| Red Hat Enterprise Linux 9 | pcs-0:0.11.1-10.el9_0.1 | RHSA-2022:4587 |
| Red Hat Satellite 6.12 for RHEL 8 | rubygem-sinatra-1:2.2.0-1.el8sat | RHSA-2022:8506 |
Frequently Asked Questions
Is GHSA-qp49-3pvw-x4m5 in your dependencies?
O3 Security finds GHSA-qp49-3pvw-x4m5 across RubyGems dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.