Answer in brief
CVE-2026-61846 records a Medium severity vulnerability in Crass: Deeply nested CSS blocks and functions can trigger a SystemStackError or excessive memory usage. The current sources do not mark it as known exploited. The current feed maps crass (rubygems), crass (rubygems). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps crass (rubygems), crass (rubygems). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| crassrubygems | <1.0.7 | 1.0.7 |
| crassrubygems | >=0 <1.0.7 | 1.0.7 |
Published upstream
Oct 29, 2026
Evidence: source:ghsa:source_dates:source-dates:recordSource modified
Oct 29, 2026
Evidence: source:ghsa:source_dates:source-dates:recordFirst seen by HOL
Oct 29, 2026
### Impact Crass recursively parses CSS simple blocks and functions without a depth guard. An attacker-controlled value containing many deeply nested blocks can recurse until Ruby raises `SystemStackError: stack level too deep`, or can cause excessive memory usage. ### Patches This is fixed in Crass 1.0.7, which adds a configurable depth limit with a conservative default. ### Workarounds Add `SystemStackError` handling around Crass calls in your application. Buy more RAM.
Quoted source text, attributed separately from HOL analysis.