Is rack-cors 0.4 vulnerable?
RubyGems · 2 releases from 0.4.0 to 0.4.1 · latest rack-cors is 3.0.0 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. rack-cors 0.4.1, the last 0.4 release, is affected by 1 known security advisory (1 medium), including CVE-2019-18978. 1 more affects earlier 0.4.x releases. Upgrade to 1.0.4 or later to fix all of them.
bundle update --conservative rack-cors # Gemfile: '>= 1.0.4'Is your project on an affected rack-cors?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting rack-cors 0.4.1
The rack-cors rubygem may allow directory traveral
- Affected
- <1.0.4
- Fixed in
- 1.0.4
Fixed within 0.4.x, affecting earlier releases
Missing Regex anchor in Rack-Cors allows malicious third party site to perform CORS request
- Affected
- <0.4.1
- Fixed in
- 0.4.1
Every rack-cors 0.4.x release
Affected: 0.4.0 to 0.4.1. Latest rack-cors: 3.0.0.
| Version | Known advisories |
|---|---|
| rack-cors 0.4.1 | CVE-2019-18978 |
| rack-cors 0.4.0 | CVE-2019-18978, CVE-2017-11173 |
Which of your client projects are still on rack-cors 0.4?
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.