Skip to main content
VulnerabilityPublished

CVE-2026-61847: rgrove crass · Uncontrolled Recursion

Affects rgrove crassSource CVE Database V5

0
Compare

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

Data as of 30 Oct 2026, 20:38 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.06.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:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 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 30 Oct 2026.

What to do

Upgrade rgrove crass to 1.0.7.

Affected software

ProductAffectedFixed in
rgrovecrassAffected
  • <1.0.7
Fixed in
  • 1.0.7
RubyGemscrasspkg:gem/crassOther threatsAffected
  • <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 this uncontrolled recursion issue is fixed. Using the :preserve_comments option also avoids the vulnerable recursive path, but the recommended approach is to apply the official fix by upgrading.

Description

CVE-2026-61847 is a vulnerability in the Ruby CSS parser Crass prior to version 1.0.7. When the default setting to discard CSS comments is used, an attacker can craft a stylesheet with many adjacent comments that cause uncontrolled recursion, leading to a SystemStackError and denial of service. This issue is resolved in Crass version 1.0.7 by changing how comments are handled.

References

Community reviews

Loading reviews…