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.
This is fixed in Crass 1.0.7.
Avoid passing non-ASCII input to Crass. Or cultivate patience.
{
"cwe_ids": [
"CWE-400"
],
"github_reviewed": true,
"github_reviewed_at": "2026-10-29T16:35:29Z",
"nvd_published_at": null,
"severity": "MODERATE"
}