Crass is a Ruby CSS parser that's fully compliant with the CSS Syntax Level 3 specification. Prior to 1.0.7, when the `:preserve_comments` option is not enabled, which is the default, Crass discards CSS comments by recursively consuming the next token. An attacker-provided stylesheet containing a very large number of adjacent comments can cause excessive recursion and trigger a `SystemStackError`, denying service to the parsing application. Preserving comments avoids this recursive path. This issue is fixed in version 1.0.7.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 1
- First seenCVSS 6.3 · rgroveNVD modified 2026-10-30 18:44
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 3
- https://github.com/rgrove/crass/security/advisories/GHSA-wwpr-jff3-395c x_refsource_confirm
- https://github.com/rgrove/crass/commit/25d78cc607c54262e9d43ea1930f3ba5bb03dfb5 x_refsource_misc
- https://github.com/rgrove/crass/releases/tag/v1.0.7 x_refsource_misc