Quick answers
- Is CVE-2026-61845 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-61845 being exploited in the wild.
- How severe is CVE-2026-61845?
- High severity, with a CVSS score of 4, published 30 October 2026.
- Which products and versions are affected?
- Rgrove Crass < 1.0.7; crass (RubyGems) < 1.0.7, ECOSYSTEM:introduced=0,fixed=1.0.7.
- Is there a fix for CVE-2026-61845?
- Yes. crass (RubyGems): upgrade to 1.0.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-61845 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-61845?
- Check whether you run Rgrove Crass or crass (RubyGems) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- crass (RubyGems): upgrade to 1.0.7 or later
bundle update crass
Technical details
The vulnerability is an uncontrolled recursion or unbounded computation in CSS scientific notation parsing. Crass performs exponentiation on numeric values before clamping the result to Float::MAX, allowing attackers to craft tiny CSS payloads with large exponents that trigger excessive CPU and memory consumption. The flaw is in the parsing logic and can be exploited via network if the application exposes CSS parsing to untrusted input.
Affected products
- rgrove Crass < 1.0.7
Identifiers
- CVE-2026-61845
- GHSA-6wmf-3r64-vcwv
Timeline
- 2026-06-25: disclosed
- 2026-10-20: advisory