<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-03T23:01:17.806073+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-61848</id>
    <title>fkie_cve-2026-61848</title>
    <updated>2026-11-03T23:01:17.833457+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Crass is a Ruby CSS parser that's fully compliant with the CSS Syntax Level 3 specification. Prior to 1.0.7, when Crass parses input containing `non-ASCII characters`, inefficiencies in tracking the positions of `multi-byte characters` result in superlinear parsing time. An attacker-controlled CSS input consisting of many `non-ASCII characters` can therefore cause excessive CPU consumption and potentially denial of service. This issue is fixed in version 1.0.7.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-61848"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-8vfg-2r28-hvhj</id>
    <title>GHSA-8vfg-2r28-hvhj — Crass: Non-ASCII characters cause superlinear CPU consumption</title>
    <updated>2026-11-03T23:01:17.833522+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> RubyGems: crass</p>
<p>### Impact</p>
<p>When parsing an input containing non-ASCII characters, inefficiencies in how Crass tracks the positions of multi-byte characters result in superlinear parsing time. An attacker-controlled input consisting of many non-ASCII characters could cause excessive CPU consumption and potentially denial of service.</p>
<p>### Patches</p>
<p>This is fixed in Crass 1.0.7.</p>
<p>### Workarounds</p>
<p>Avoid passing non-ASCII input to Crass. Or cultivate patience.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-8vfg-2r28-hvhj"/>
  </entry>
</feed>
