HighGHSA-qp49-3pvw-x4m5CVE-2022-29970

sinatra does not validate expanded path matches

Published 3 May 2022 · Updated 4 Nov 2025

Is your project on an affected sinatra?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

sinatraRubyGems
Affected
<2.2.0
Fixed in
2.2.0
Update to the fixed version for your release line, for example:bundle update --conservative sinatra # Gemfile: '>= 2.2.0'

Details

Sinatra before 2.2.0 does not validate that the expanded path matches public_dir when serving static files.

Is GHSA-qp49-3pvw-x4m5 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected sinatra, and gives you the command that fixes it.

More advisories for sinatra

  • LowCVE-2025-61921Sinatra is vulnerable to ReDoS through ETag header value generation · 10 Oct 2025
  • MediumCVE-2024-21510Sinatra vulnerable to Reliance on Untrusted Inputs in a Security Decision · 1 Nov 2024
  • HighCVE-2022-45442Sinatra vulnerable to Reflected File Download attack · 30 Nov 2022
  • MediumCVE-2018-11627Sinatra Cross-site Scripting vulnerability · 5 Jun 2018
  • MediumCVE-2018-7212Sinatra Path Traversal vulnerability · 20 Feb 2018
sinatra security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.