Summary
Crass: Deeply nested CSS blocks and functions can trigger a SystemStackError or excessive memory usage
Workarounds
Add SystemStackError handling around Crass calls in your application. Buy more RAM.
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.
Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
This is fixed in Crass 1.0.7, which adds a configurable depth limit with a conservative default.
Frequently Asked Questions
- What is CVE-2026-61846? CVE-2026-61846 is a medium-severity uncontrolled resource consumption vulnerability in crass (rubygems), affecting versions < 1.0.7. It is fixed in 1.0.7. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
- Which versions of crass are affected by CVE-2026-61846? crass (rubygems) versions < 1.0.7 is affected.
- Is there a fix for CVE-2026-61846? Yes. CVE-2026-61846 is fixed in 1.0.7. Upgrade to this version or later.
- Is CVE-2026-61846 exploitable, and should I be worried? Whether CVE-2026-61846 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-61846 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-61846? Upgrade
crassto 1.0.7 or later.