CVE-2026-61848: Crass · Non-ASCII characters cause superlinear CPU consumption
Affects crassSource GCVE Database
Not known to be exploited · CVSS 6.3 Medium : upgrade to 1.0.7 when convenient.
Data as of 29 Oct 2026, 17:11 UTC
- Patch
- Available – fixed in 1.0.7
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:LExploitation evidence
Disclosed: evidence found.
CVE published 29 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade crass to 1.0.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| RubyGemscrass | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Crass to version 1.0.7 or later to apply the official fix. Alternatively, avoid passing non-ASCII input to Crass to prevent triggering the vulnerability.
Description
Crass versions prior to 1.0.7 have a vulnerability where parsing input containing non-ASCII characters leads to superlinear CPU consumption due to inefficient tracking of multi-byte character positions. This can be exploited by an attacker to cause excessive CPU usage and potential denial of service. The issue is fixed in version 1.0.7.