PatchSiren cyber security CVE debrief
CVE-2026-61847 rgrove CVE debrief
A large number of adjacent CSS comments can trigger a SystemStackError in Crass versions before 1.0.7. This issue arises when the `:preserve_comments` option is not enabled, which is the default behavior. An attacker providing a stylesheet with many adjacent comments can cause excessive recursion, leading to a `SystemStackError`. The issue is fixed in Crass 1.0.7, which no longer recurses when discarding comments. A workaround is to set the `:preserve_comments` option to `true`, which prevents recursion when comments are preserved.
- Vendor
- rgrove
- Product
- crass
- CVSS
- MEDIUM 6.3
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-29
- Original CVE updated
- 2026-10-29
- Advisory published
- 2026-10-29
- Advisory updated
- 2026-10-29
Who should care
Defenders responsible for systems that process CSS stylesheets from untrusted sources should be aware of this vulnerability and take steps to mitigate it. This includes upgrading to Crass 1.0.7 or applying the recommended workaround.
Why it matters
Defenders should prioritize upgrading to Crass 1.0.7 or applying the workaround to prevent potential denial-of-service attacks. This is particularly important for systems that process CSS stylesheets from untrusted sources.
- Potential denial-of-service attacks through excessive recursion
- Need to verify and upgrade to Crass 1.0.7 or later
- Possible impact on systems processing untrusted CSS stylesheets
Technical summary
The Crass library is vulnerable to a denial-of-service attack when processing a large number of adjacent CSS comments. This occurs when the `:preserve_comments` option is not enabled, causing excessive recursion and leading to a `SystemStackError`. The issue is fixed in Crass 1.0.7, which no longer recurses when discarding comments. An attacker providing a stylesheet with many adjacent comments can cause excessive recursion, leading to a `SystemStackError`. Defenders should prioritize upgrading to Crass 1.0.7 or applying the workaround to prevent potential denial-of-service attacks.
Defensive priority
Defenders should prioritize upgrading to Crass 1.0.7 or applying the workaround to prevent potential denial-of-service attacks. This is particularly important for systems that process CSS stylesheets from untrusted sources.
Recommended defensive actions
- Upgrade to Crass 1.0.7 or later
- Apply the workaround by setting the `:preserve_comments` option to `true`
- Review and update CSS processing systems to handle untrusted sources
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
Evidence notes
The CVE record and source item provide details about the vulnerability, its impact, and the fix. However, there is limited information about potential exploits or attacks in the wild. Defenders should verify the affected scope and severity, and review compensating controls for exposed systems. The Crass library is vulnerable to a denial-of-service attack when processing a large number of adjacent CSS comments. This occurs when the `:preserve_comments` option is not enabled, causing excessive recursion and leading to a `SystemStackErro
Sources and references
Verified primary and authoritative sources
-
CVE-2026-61847 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-61847
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-61847 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-61847
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Crass: A large number of adjacent CSS comments can trigger a SystemStackError
Unverified legacy reference
URL: https://storage.googleapis.com/osv-vulnerabilities/RubyGems/GHSA-wwpr-jff3-395c.json
osv_dev
-
Source reference
Unverified legacy reference
URL: https://github.com/rgrove/crass/security/advisories/GHSA-wwpr-jff3-395c
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://github.com/rgrove/crass/commit/25d78cc607c54262e9d43ea1930f3ba5bb03dfb5
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://github.com/rgrove/crass
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://github.com/rgrove/crass/releases/tag/v1.0.7
Supplemental source
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.