Is sprockets 2.12 vulnerable?
RubyGems · 6 releases from 2.12.0 to 2.12.5 · latest sprockets is 4.4.1 · checked 18 Nov 2026
No known advisories in the last release
sprockets 2.12.5, the last 2.12 release, has no known advisories. 2 advisories affect earlier 2.12.x releases, so update to 2.12.5.
bundle update --conservative sprockets # Gemfile: '>= 2.12.5'Is your project on an affected sprockets?
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.12.x, affecting earlier releases
Sprockets path traversal leads to information leak
- Affected
- >=3.0.0 <3.7.2 · >=4.0.0.beta1 <4.0.0.beta8 · <2.12.5
- Fixed in
- 2.12.5, 3.7.2, 4.0.0.beta8
sprockets vulnerable to Path Traversal
- Affected
- <2.0.5 · >=2.1.0 <2.1.4 · >=2.2.0 <2.2.3 · >=2.3.0 <2.3.3 · >=2.4.0 <2.4.6 · >=2.5.0 <2.5.1 · >=2.6.0 <2.7.1 · >=2.8.0 <2.8.3 · >=2.9.0 <2.9.4 · >=2.10.0 <2.10.2 · >=2.11.0 <2.11.3 · >=2.12.0 <2.12.3
- Fixed in
- 2.0.5, 2.1.4, 2.2.3, 2.3.3, 2.4.6, 2.5.1, 2.7.1, 2.8.3, 2.9.4, 2.10.2, 2.11.3, 2.12.3
Every sprockets 2.12.x release
Affected: 2.12.0 to 2.12.4. 2.12.5 is not affected. Latest sprockets: 4.4.1.
| Version | Known advisories |
|---|---|
| sprockets 2.12.5 | None |
| sprockets 2.12.4 | CVE-2018-3760 |
| sprockets 2.12.3 | CVE-2018-3760 |
| sprockets 2.12.2 | CVE-2018-3760, CVE-2014-7819 |
| sprockets 2.12.1 | CVE-2018-3760, CVE-2014-7819 |
| sprockets 2.12.0 | CVE-2018-3760, CVE-2014-7819 |
Which of your client projects are still on sprockets 2.12?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact sprockets version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other sprockets 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.