Skip to main content
VulnerabilityPublished

CVE-2026-61847: Crass · A large number of adjacent CSS comments can trigger a SystemStackError

Affects crassSource GCVE Database

0
Compare

Not known to be exploited · CVSS 6.3 Medium : upgrade to 1.0.7 when convenient.

Data as of 29 Oct 2026, 17:11 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
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:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 29 Oct 2026.

What to do

Upgrade crass to 1.0.7.

Affected software

ProductAffectedFixed in
RubyGemscrassAffected
  • <1.0.7
Fixed in
  • 1.0.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to Crass version 1.0.7 or later, where the recursion issue is fixed. Alternatively, if upgrading is not immediately possible, set the :preserve_comments option to true to prevent recursion and avoid the SystemStackError. No other mitigation is required.

Description

Crass versions prior to 1.0.7 contain a vulnerability where processing a stylesheet with a large number of adjacent CSS comments causes excessive recursion, leading to a SystemStackError. This occurs when the default behavior of discarding comments is used (i.e., :preserve_comments option is false). The issue is fixed in version 1.0.7, which eliminates recursion when discarding comments. As a workaround, enabling the :preserve_comments option prevents the recursion and the error.

References

Community reviews

Loading reviews…