<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 16 Nov 2026 20:23:31 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-393879</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-393879</link>
      <description>EUVD-2026-393879</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-393879</guid>
    </item>
    <item>
      <title>fkie_cve-2026-116695</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-116695</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-116695</guid>
    </item>
    <item>
      <title>GHSA-pq4g-8rxf-4g29 — Crass: Incorrect tokenization of bad URLs enables CSS sanitizer bypass</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-pq4g-8rxf-4g29</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: crass&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;Crass&amp;#39;s tokenizer didn&amp;#39;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.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;While 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.&lt;/p&gt;
&lt;p&gt;Browsers terminate the bad URL at that `)`, so everything Crass treated as part of the bad URL is live CSS to a browser.&lt;/p&gt;
&lt;p&gt;This bug has existed in every released version of Crass.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Crass by itself only mis-tokenizes input. The security impact is on CSS sanitizers that use Crass to make allow/deny decisions and then re-serialize the CSS. Exploitation requires a sanitizer that doesn&amp;#39;t reject bad URL tokens wherever they occur. Confirmed examples (verified in Chromium against the sanitizers&amp;#39; output):&lt;/p&gt;
&lt;p&gt;- **Sanitize** (all versions through 7…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: crass&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;Crass&amp;#39;s tokenizer didn&amp;#39;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.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;While 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.&lt;/p&gt;
&lt;p&gt;Browsers terminate the bad URL at that `)`, so everything Crass treated as part of the bad URL is live CSS to a browser.&lt;/p&gt;
&lt;p&gt;This bug has existed in every released version of Crass.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Crass by itself only mis-tokenizes input. The security impact is on CSS sanitizers that use Crass to make allow/deny decisions and then re-serialize the CSS. Exploitation requires a sanitizer that doesn&amp;#39;t reject bad URL tokens wherever they occur. Confirmed examples (verified in Chromium against the sanitizers&amp;#39; output):&lt;/p&gt;
&lt;p&gt;- **Sanitize** (all versions through 7…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-pq4g-8rxf-4g29</guid>
    </item>
    <item>
      <title>OESA-2026-4724 — rubygem-crass security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-4724</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP3: rubygem-crass&lt;/p&gt;
&lt;p&gt;Crass is a pure Ruby CSS parser based on the CSS Syntax Level 3 spec.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;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.(CVE-2026-116695)&lt;/p&gt;
&lt;p&gt;Crass is a Ruby CSS parser that&amp;amp;apos;s fully compliant with the CSS Syntax Level 3 specification. Prior to 1.0.7, Crass recursively parses `CSS simple blocks and functions` without a depth guard. An attacker-controlled CSS value containing deeply nested blocks or functions can recurse until Ruby raises `SystemStackError`: stack level too deep, or cause excessive memory usage. Version 1.0.7 adds a configurable depth limit with a conservative default. This issue is fixed in version 1.0.7.(CVE-2026-61846)&lt;/p&gt;
&lt;p&gt;Crass is a Ruby CSS parser that&amp;amp;apos;s fully compliant with the CSS Syntax Level 3 specification. Prior to 1.0.7, when the `:preserve_comments` option is not enabled, which is the default, Crass discards CSS comments b…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP3: rubygem-crass&lt;/p&gt;
&lt;p&gt;Crass is a pure Ruby CSS parser based on the CSS Syntax Level 3 spec.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;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.(CVE-2026-116695)&lt;/p&gt;
&lt;p&gt;Crass is a Ruby CSS parser that&amp;amp;apos;s fully compliant with the CSS Syntax Level 3 specification. Prior to 1.0.7, Crass recursively parses `CSS simple blocks and functions` without a depth guard. An attacker-controlled CSS value containing deeply nested blocks or functions can recurse until Ruby raises `SystemStackError`: stack level too deep, or cause excessive memory usage. Version 1.0.7 adds a configurable depth limit with a conservative default. This issue is fixed in version 1.0.7.(CVE-2026-61846)&lt;/p&gt;
&lt;p&gt;Crass is a Ruby CSS parser that&amp;amp;apos;s fully compliant with the CSS Syntax Level 3 specification. Prior to 1.0.7, when the `:preserve_comments` option is not enabled, which is the default, Crass discards CSS comments b…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-4724</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-116695</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-116695</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: ruby-crass, Ubuntu:18.04:LTS: ruby-crass, Ubuntu:20.04:LTS: ruby-crass, Ubuntu:22.04:LTS: ruby-crass, Ubuntu:24.04:LTS: ruby-crass, Ubuntu:26.10: ruby-crass, Ubuntu:26.04:LTS: ruby-crass&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: ruby-crass, Ubuntu:18.04:LTS: ruby-crass, Ubuntu:20.04:LTS: ruby-crass, Ubuntu:22.04:LTS: ruby-crass, Ubuntu:24.04:LTS: ruby-crass, Ubuntu:26.10: ruby-crass, Ubuntu:26.04:LTS: ruby-crass&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-116695</guid>
    </item>
  </channel>
</rss>
