{"items":[{"id":"NVI-00009122","kind":"vulnerability","title":"Crass: Incorrect tokenization of bad URLs enables CSS sanitizer bypass","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-pq4g-8rxf-4g29","CVE-2026-116695"],"plain_summary":"GitHub lists this reviewed advisory for crass. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-1de80d9a60718c4a08598c284e3c7b74"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"0.353%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.29027. Missing scores are unknown.","source_id":"sr-1de80d9a60718c4a08598c284e3c7b74"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-bc0c2890cab5e687cf952491cfb247bd","url":"https://github.com/advisories/GHSA-pq4g-8rxf-4g29","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-pq4g-8rxf-4g29","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:56:08.420Z"},{"id":"sr-1de80d9a60718c4a08598c284e3c7b74","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-116695","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:15:58.843Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-bc0c2890cab5e687cf952491cfb247bd"],"technology":"crass","known_exclusions":[],"conditions_summary":"## Summary\n\nCrass's tokenizer didn't terminate a bad URL token at a `)` that followed an escaped backslash (`\\\\`). As a result, Crass consumed more input as part of the bad URL than a spec-compliant browser does. CSS sanitizers that parse untrusted CSS with Crass and re-emit it could be tricked into passing through declarations, style rules, or at-rules (including `@import`) that the sanitizer would otherwise have removed, but that a browser would then parse and apply.\n\n## Details\n\nWhile consuming the remnants of a bad URL (CSS Syntax Level 3, §4.3.15), Crass checked whether the *previously consumed* code point and the next code point formed a valid escape, in addition to checking the next two unconsumed code points. After an escaped backslash, the previously consumed code point is a backslash, so a following `)` was incorrectly treated as escaped and the bad URL token continued until the next unescaped `)` or the end of the input.\n\nBrowsers terminate the bad URL at that `)`, so everything Crass treated as part of the bad URL is live CSS to a browser.\n\nThis bug has existed in every released version of Crass.\n\n## Impact\n\nCrass by itself only mis-tokenizes input. The security impact ","public_affected_ranges":["<= 1.0.7"]}],"null_published_at":"2026-11-07T14:01:58.727Z","source_updated_at":"2026-10-28T22:42:53.000Z","source_disclosed_at":"2026-10-28T22:42:53.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:56:08.420Z"},{"id":"NVI-00009122","kind":"vulnerability","title":"Crass: Incorrect tokenization of bad URLs enables CSS sanitizer bypass","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-pq4g-8rxf-4g29","CVE-2026-116695"],"plain_summary":"GitHub lists this reviewed advisory for crass. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-148471cc7f91d600f8542daf11c57e27"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.353%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.29037. Missing scores are unknown.","source_id":"sr-148471cc7f91d600f8542daf11c57e27"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-bc0c2890cab5e687cf952491cfb247bd","url":"https://github.com/advisories/GHSA-pq4g-8rxf-4g29","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-pq4g-8rxf-4g29","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:56:08.420Z"},{"id":"sr-148471cc7f91d600f8542daf11c57e27","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-116695","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:28:32.267Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-bc0c2890cab5e687cf952491cfb247bd"],"technology":"crass","known_exclusions":[],"conditions_summary":"## Summary\n\nCrass's tokenizer didn't terminate a bad URL token at a `)` that followed an escaped backslash (`\\\\`). As a result, Crass consumed more input as part of the bad URL than a spec-compliant browser does. CSS sanitizers that parse untrusted CSS with Crass and re-emit it could be tricked into passing through declarations, style rules, or at-rules (including `@import`) that the sanitizer would otherwise have removed, but that a browser would then parse and apply.\n\n## Details\n\nWhile consuming the remnants of a bad URL (CSS Syntax Level 3, §4.3.15), Crass checked whether the *previously consumed* code point and the next code point formed a valid escape, in addition to checking the next two unconsumed code points. After an escaped backslash, the previously consumed code point is a backslash, so a following `)` was incorrectly treated as escaped and the bad URL token continued until the next unescaped `)` or the end of the input.\n\nBrowsers terminate the bad URL at that `)`, so everything Crass treated as part of the bad URL is live CSS to a browser.\n\nThis bug has existed in every released version of Crass.\n\n## Impact\n\nCrass by itself only mis-tokenizes input. The security impact ","public_affected_ranges":["<= 1.0.7"]}],"null_published_at":"2026-11-03T17:49:18.483Z","source_updated_at":"2026-10-28T22:42:53.000Z","source_disclosed_at":"2026-10-28T22:42:53.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:56:08.420Z"},{"id":"NVI-00009122","kind":"vulnerability","title":"Crass: Incorrect tokenization of bad URLs enables CSS sanitizer bypass","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-pq4g-8rxf-4g29","CVE-2026-116695"],"plain_summary":"GitHub lists this reviewed advisory for crass. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-bc0c2890cab5e687cf952491cfb247bd"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-bc0c2890cab5e687cf952491cfb247bd","url":"https://github.com/advisories/GHSA-pq4g-8rxf-4g29","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-pq4g-8rxf-4g29","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:56:08.420Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-bc0c2890cab5e687cf952491cfb247bd"],"technology":"crass","known_exclusions":[],"conditions_summary":"## Summary\n\nCrass's tokenizer didn't terminate a bad URL token at a `)` that followed an escaped backslash (`\\\\`). As a result, Crass consumed more input as part of the bad URL than a spec-compliant browser does. CSS sanitizers that parse untrusted CSS with Crass and re-emit it could be tricked into passing through declarations, style rules, or at-rules (including `@import`) that the sanitizer would otherwise have removed, but that a browser would then parse and apply.\n\n## Details\n\nWhile consuming the remnants of a bad URL (CSS Syntax Level 3, §4.3.15), Crass checked whether the *previously consumed* code point and the next code point formed a valid escape, in addition to checking the next two unconsumed code points. After an escaped backslash, the previously consumed code point is a backslash, so a following `)` was incorrectly treated as escaped and the bad URL token continued until the next unescaped `)` or the end of the input.\n\nBrowsers terminate the bad URL at that `)`, so everything Crass treated as part of the bad URL is live CSS to a browser.\n\nThis bug has existed in every released version of Crass.\n\n## Impact\n\nCrass by itself only mis-tokenizes input. The security impact ","public_affected_ranges":["<= 1.0.7"]}],"null_published_at":"2026-10-31T22:13:31.284Z","source_updated_at":"2026-10-28T22:42:53.000Z","source_disclosed_at":"2026-10-28T22:42:53.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:56:08.420Z"}],"next_cursor":null,"snapshot_revision":"42594"}