Crass: Deeply nested CSS blocks and functions can trigger a SystemStackError or excessive memory usage
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
Crass recursively parses CSS simple blocks and functions without a depth guard. An attacker-controlled value containing many deeply nested blocks can recurse until Ruby raises SystemStackError: stack level too deep, or can cause excessive memory usage.
Patches
This is fixed in Crass 1.0.7, which adds a configurable depth limit with a conservative default.
Workarounds
Add SystemStackError handling around Crass calls in your application. Buy more RAM.
Is GHSA-6jxj-px6v-747w 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-61848Crass: Non-ASCII characters cause superlinear CPU consumption · 29 Oct 2026
- MediumCVE-2026-61847Crass: A large number of adjacent CSS comments can trigger a SystemStackError · 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.