All reports
Medium

Crass: Non-ASCII characters cause superlinear CPU consumption

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
RubyGemscrass
Affected versions
< 1.0.7
Fixed version
1.0.7

Exploitation

CVE-2026-61848

Probability of exploitation in the next 30 days: 0.45%

FIRST EPSS · 2026-11-21

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.

Links

Credits

  • hourianto
  • rgrove