CVE-2026-61847: Ruby crass · Crass is a Ruby CSS parser that's fully compliant with the CSS Syntax Level 3 specification
Affects ruby-crassSource GCVE Database
Not known to be exploited · CVSS 6.3 Medium · fixed in 1.0.7 : update ruby-crass when convenient.
Data as of 5 Nov 2026, 12:34 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 6.3 |
|---|
- Patch
- Available – fixed in 1.0.7
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:LExploitation evidence
Disclosed: evidence found.
CVE published 30 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10ruby-crasspkg:deb/ubuntu/ruby-crass?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSruby-crasspkg:deb/ubuntu/ruby-crass?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSruby-crasspkg:deb/ubuntu/ruby-crass?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Ubuntu 22.04 LTSruby-crasspkg:deb/ubuntu/ruby-crass?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Ubuntu 20.04 LTSruby-crasspkg:deb/ubuntu/ruby-crass?arch=source&distro=focalOther threats | Affected
| Fixed in– |
Ubuntu 18.04 LTSruby-crasspkg:deb/ubuntu/ruby-crass?arch=source&distro=bionicOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
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.
References
- ubuntu.com/security/CVE-2026-61847 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-61847 (opens in a new tab)
- github.com/rgrove/crass/security/advisories/GHSA-wwpr-jff3-395c (opens in a new tab)
- github.com/rgrove/crass/commit/25d78cc607c54262e9d43ea1930f3ba5bb03dfb5 (opens in a new tab)
- github.com/rgrove/crass/releases/tag/v1.0.7 (opens in a new tab)