CVEvulnerability

CVE-2026-61847

6.3 MEDIUM EPSS 0.49% Published 2026-10-30 Modified 2026-10-30 Official page ↗

Exploitation and prioritisation

EPSS
0.49% chance of exploitation in the next 30 days · in the top 58.1% of all CVEs (2026-11-03)
CISA SSVC: exploitation
none
CISA SSVC: automatable
no
CISA SSVC: technical impact
partial
EU Vulnerability Database
EUVD-2026-114323

Affected packages

EcosystemPackageVulnerableFixed inAdvisory
RubyGemscrass< 1.0.71.0.7GHSA-wwpr-jff3-395c
Status
Deferred
Published
2026-10-30
Last modified
2026-10-30
Assigner
[email protected]
CVSS 4.0 ([email protected])
6.3 MEDIUM — 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Weaknesses
CWE-674

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.

Related

Weakness · CWE (1)

  • CWE-674 Uncontrolled Recursion weakness

Referenced by GitHub Advisory · alias (1)

  • GHSA-wwpr-jff3-395c Crass: A large number of adjacent CSS comments can trigger a SystemStackError advisory · RubyGems

References