Answer in brief
CVE-2026-61848 records a Medium severity vulnerability in Crass: Non-ASCII characters cause superlinear CPU consumption. 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 When parsing an input containing non-ASCII characters, inefficiencies in how Crass tracks the positions of multi-byte characters result in superlinear parsing time. An attacker-controlled input consisting of many non-ASCII characters could cause excessive CPU consumption and potentially denial of service. ### Patches This is fixed in Crass 1.0.7. ### Workarounds Avoid passing non-ASCII input to Crass. Or cultivate patience.
Quoted source text, attributed separately from HOL analysis.