Crass: Non-ASCII characters cause superlinear CPU consumption
RSS Feed
MODERATE
GHSA-8vfg-2r28-hvhj
CVE-2026-61848
Description:
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.
Affected Packages
| Ecosystem | Package | Vulnerable Versions | Patched Version |
|---|---|---|---|
| rubygems |
crass
|
< 1.0.7 |
1.0.7
|
Actions
Advisory Details
| Published: | October 29, 2026 24 days ago |
| Updated: | November 22, 2026 about 20 hours ago |
| CVSS Score: | 6.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L |
| EPSS: | 0.45% 40th percentile |
| Source: | Github |
| Classification: | GENERAL |
| UUID: | GSA_kwCzR0hTQS04dmZnLTJyMjgtaHZoas4AB_9W |
PR Statistics
PR Status
Open
1 (50.0%)
Merged
0 (0.0%)
Closed
1 (50.0%)
Update Types
Patch
2 (100.0%)