Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
Check your stack
GHSA-8vfg-2r28-hvhjmedium6.3

Crass: Non-ASCII characters cause superlinear CPU consumption

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.

Source excerpt · OSV

Affected packages

Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.

crass RubyGems
Affected range Recorded fix
Earlier releases before 1.0.7Ecosystem versions1.0.7

Version evidence: OSV · GHSA-8vfg-2r28-hvhj

View original version evidence (12 explicit versions)

Affected products

Vendor version evidence. Product records are separate from automatic dependency matching.

rgrove · GitHub_M

crass

1 range

Compare with this publisher’s ranges. This does not inspect your installation.

affected

< 1.0.7

unaffected

unknown

Other versions: unknown

Original source 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.

Inside the record

Evidence available

Package identity
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers · not supplied

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-61848

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-400 ↗

CWE-400: Uncontrolled Resource Consumption

GitHub_M

Related →
Contributing organizations · 1
GitHub_M

Assigning organization

2026-10-30

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.

References

4 sources