Answer in brief
CVE-2026-116695 records a Medium severity (CVSS 5.3) vulnerability in Crass: Incorrect tokenization of bad URLs enables CSS sanitizer bypass. The current sources do not mark it as known exploited. The current feed maps rgrove/crass (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps rgrove/crass (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| rgrove/crassgeneric | <1.0.8 | 1.0.8 |
Published upstream
Oct 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 27, 2026
Crass is a Ruby CSS parser that is compliant with the CSS Syntax Level 3 specification. Prior to 1.0.8, Crass incorrectly treats a closing parenthesis after an escaped backslash as escaped while consuming the remnants of a bad URL. Crass therefore keeps declarations, style rules, or at-rules inside a bad URL token even though a browser treats them as live CSS. A sanitizer that parses untrusted CSS with Crass and reserializes it without rejecting the bad URL can allow CSS used for UI redress, external resource loading, or CSS-based data exfiltration, but this issue does not enable script execution in modern browsers. This issue is fixed in version 1.0.8.
Quoted source text, attributed separately from HOL analysis.