Crass (< 1.0.7) - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/crass--1.0.7/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioTue, 20 Oct 2026 14:43:22 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgCrass: Denial of service via CSS exponentiation (CVE-2026-61845)https://feed.craftedsignal.io/briefs/2026-10-crass-dos/Tue, 20 Oct 2026 14:43:22 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-10-crass-dos/The Crass Ruby gem is vulnerable to a denial of service condition where maliciously crafted CSS numeric exponents trigger excessive CPU and memory consumption.The Crass Ruby gem (versions prior to 1.0.7) is susceptible to a denial of service (DoS) vulnerability, identified as CVE-2026-61845. The library fails to properly validate or limit numeric exponents found in CSS strings during parsing. When an application processes attacker-controlled CSS, an attacker can submit a string containing an extremely large numeric exponent. The library attempts to calculate the result of this exponentiation before clamping it to the maximum float value, leading to disproportionate CPU and memory consumption. This resource exhaustion can result in application instability or process crashes, impacting any service that relies on Crass for sanitizing or parsing user-supplied CSS.

Impact

The vulnerability allows remote attackers to cause a denial of service on applications using the Crass library to process untrusted CSS content. Successful exploitation leads to excessive resource consumption and application crashes, potentially disrupting availability for all users of the affected service. The vulnerability affects all users of Crass versions below 1.0.7 in any sector utilizing this Ruby gem.

Recommendation

  1. Upgrade the Crass gem to version 1.0.7 or later to implement proper clamping of numeric exponents.
  2. Implement input validation and length limits for all user-supplied CSS before passing the content to the Crass parser.
  3. Monitor application error logs for memory exhaustion or process restarts occurring during CSS parsing operations.
]]>mediumadvisorydenial-of-servicerubycss