Is rack-cors 2.0 vulnerable?

RubyGems · 3 releases from 2.0.0 to 2.0.2 · latest rack-cors is 3.0.0 · checked 18 Nov 2026

No known advisories in the last release

rack-cors 2.0.2, the last 2.0 release, has no known advisories. 1 advisory affects earlier 2.0.x releases, so update to 2.0.2.

Update within 2.0:bundle update --conservative rack-cors # Gemfile: '>= 2.0.2'

Is your project on an affected rack-cors?

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

Fixed within 2.0.x, affecting earlier releases

  • MediumCVE-2024-27456GHSA-785g-282q-pwvx26 Feb 2024

    Rack CORS Middleware has Insecure File Permissions

    Affected
    >=2.0.1 <2.0.2
    Fixed in
    2.0.2

Every rack-cors 2.0.x release

Affected: 2.0.1. 2.0.2 is not affected. Latest rack-cors: 3.0.0.

VersionKnown advisories
rack-cors 2.0.2None
rack-cors 2.0.1CVE-2024-27456
rack-cors 2.0.0None

Which of your client projects are still on rack-cors 2.0?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact rack-cors version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other rack-cors versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the RubyGems registry. Refreshed daily.