Crass: Non-ASCII characters cause superlinear CPU consumption
Published 29 Oct 2026 · Updated 29 Oct 2026
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
Affected package
- Affected
- <1.0.7
- Fixed in
- 1.0.7
bundle update --conservative crass # Gemfile: '>= 1.0.7'Details
Impact
When parsing an input containing non-ASCII characters, inefficiencies in how Crass tracks the positions of multi-byte characters result in superlinear parsing time. An attacker-controlled input consisting of many non-ASCII characters could cause excessive CPU consumption and potentially denial of service.
Patches
This is fixed in Crass 1.0.7.
Workarounds
Avoid passing non-ASCII input to Crass. Or cultivate patience.
Is GHSA-8vfg-2r28-hvhj 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 crass, and gives you the command that fixes it.
More advisories for crass
- MediumCVE-2026-61847Crass: A large number of adjacent CSS comments can trigger a SystemStackError · 29 Oct 2026
- MediumCVE-2026-61846Crass: Deeply nested CSS blocks and functions can trigger a SystemStackError or excessive memory usage · 29 Oct 2026
- MediumCVE-2026-116695Crass: Incorrect tokenization of bad URLs enables CSS sanitizer bypass · 28 Oct 2026
- HighCVE-2026-61845Crass : Large numeric exponents cause CPU and memory denial of service · 20 Oct 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.