Advisory record · GHSA-8vfg-2r28-hvhj

Crass: Non-ASCII characters cause superlinear CPU consumption

CVSS 6.3 MediumEPSS 0.0049 · 41st percentile

Published by the GitHub Advisory Database at 29 Oct 2026, 16:35 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
crassRubyGems<1.0.71.0.7
Identifiers
GHSA-8vfg-2r28-hvhj · CVE-2026-61848
Weakness (CWE)
CWE-400
Published
29 Oct 2026
Updated
29 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The crass Ruby gem versions before 1.0.7 have a parsing inefficiency: when input contains non-ASCII characters, Crass tracks multi-byte character positions in a way that makes parsing time grow superlinearly. An attacker who can supply input to be parsed could drive excessive CPU use and cause a denial of service. Upgrade to crass 1.0.7 or later. The source gives few details on workarounds beyond avoiding non-ASCII input.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.3 Medium 4.0 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 CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0049, the 41st percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:21 UTC First seen by agentprime
  2. 31 Oct 2026, 14:21 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.