CVE-2026-116695: rgrove crass · Interpretation Conflict
Affects rgrove crassSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.0.8 when convenient.
Data as of 27 Oct 2026, 20:42 UTC
- Patch
- Available – fixed in 1.0.8
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 27 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade rgrove crass to 1.0.8.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| rgrovecrass | Affected
| Fixed in
|
RubyGemscrasspkg:gem/crassOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Crass to version 1.0.8 or later, where this issue is fixed.
Description
Crass, a Ruby CSS parser, has a vulnerability prior to version 1.0.8 where it incorrectly treats a closing parenthesis after an escaped backslash as escaped when parsing bad URLs. This causes Crass to retain CSS declarations inside a bad URL token that browsers would normally treat as live CSS. This can allow CSS-based UI redress, external resource loading, or data exfiltration when sanitizing untrusted CSS, but it does not enable script execution in modern browsers. The issue is fixed in version 1.0.8.