Is crass 0.2 vulnerable?
RubyGems · 2 releases from 0.2.0 to 0.2.1 · latest crass is 1.0.8 · checked 18 Nov 2026
Yes: 5 known advisories
Yes. crass 0.2.1, the last 0.2 release, is affected by 5 known security advisories (1 high, 4 medium), including CVE-2026-61845, CVE-2026-61848, CVE-2026-61847. Upgrade to 1.0.8 or later to fix all of them.
bundle update --conservative crass # Gemfile: '>= 1.0.8'Is your project on an affected crass?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting crass 0.2.1
Crass: Non-ASCII characters cause superlinear CPU consumption
- Affected
- <1.0.7
- Fixed in
- 1.0.7
Crass: A large number of adjacent CSS comments can trigger a SystemStackError
- Affected
- <1.0.7
- Fixed in
- 1.0.7
Crass: Deeply nested CSS blocks and functions can trigger a SystemStackError or excessive memory usage
- Affected
- <1.0.7
- Fixed in
- 1.0.7
Crass: Incorrect tokenization of bad URLs enables CSS sanitizer bypass
- Affected
- <1.0.8
- Fixed in
- 1.0.8
Crass : Large numeric exponents cause CPU and memory denial of service
- Affected
- <1.0.7
- Fixed in
- 1.0.7
Every crass 0.2.x release
Affected: 0.2.0 to 0.2.1. Latest crass: 1.0.8.
| Version | Known advisories |
|---|---|
| crass 0.2.1 | CVE-2026-61848, CVE-2026-61847, CVE-2026-61846, CVE-2026-116695, CVE-2026-61845 |
| crass 0.2.0 | CVE-2026-61848, CVE-2026-61847, CVE-2026-61846, CVE-2026-116695, CVE-2026-61845 |
Which of your client projects are still on crass 0.2?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact crass version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other crass 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.