<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-16T16:54:53.085769+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/euvd-2026-398632</id>
    <title>EUVD-2026-398632</title>
    <updated>2026-11-16T16:54:53.112488+00:00</updated>
    <content>EUVD-2026-398632</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-398632"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-61847</id>
    <title>fkie_cve-2026-61847</title>
    <updated>2026-11-16T16:54:53.112540+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 the `:preserve_comments` option is not enabled, which is the default, Crass discards CSS comments by recursively consuming the next token. An attacker-provided stylesheet containing a very large number of adjacent comments can cause excessive recursion and trigger a `SystemStackError`, denying service to the parsing application. Preserving comments avoids this recursive path. This issue is fixed in version 1.0.7.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-61847"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-wwpr-jff3-395c</id>
    <title>GHSA-wwpr-jff3-395c — Crass: A large number of adjacent CSS comments can trigger a SystemStackError</title>
    <updated>2026-11-16T16:54:53.112592+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 the `:preserve_comments` option is not enabled (which is the default behavior), Crass discards CSS comments by recursively consuming the next token. An attacker who provides a stylesheet containing a very large number of adjacent comments can cause excessive recursion and trigger a `SystemStackError`.</p>
<p>### Patches</p>
<p>This is fixed in Crass 1.0.7, which no longer recurses when discarding comments.</p>
<p>### Workarounds</p>
<p>Set the `:preserve_comments` option to `true` if this is acceptable to your use case (recursion doesn't occur when comments are preserved).</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-wwpr-jff3-395c"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2026-4724</id>
    <title>OESA-2026-4724 — rubygem-crass security update</title>
    <updated>2026-11-16T16:54:53.112645+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:24.03-LTS-SP3: rubygem-crass</p>
<p>Crass is a pure Ruby CSS parser based on the CSS Syntax Level 3 spec.

Security Fix(es):</p>
<p>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)</p>
<p>Crass is a Ruby CSS parser that&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)</p>
<p>Crass is a Ruby CSS parser that&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…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2026-4724"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rhsa-2026:100120</id>
    <title>RHSA-2026:100120 — Red Hat Security Advisory: Satellite 6.19.6 Async Update</title>
    <updated>2026-11-16T16:54:53.112730+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>sequoia-openpgp: sequoia-openpgp: Cryptographic integrity compromise via key flag confusion crass: crass: Denial of Service via crafted scientific notation in CSS crass: crass: Denial of Service via excessive recursion when processing comments rubygem-katello: Cross-tenant Content View Filter rule access and modification via unauthorized parent filter lookup foreman: authorization flaw in the Foreman::Controller::UserAware#find_user handling used by Api::V2::PersonalAccessTokensController foreman: authorization flaw in the mail-notification endpoints implemented by Api::V2::MailNotificationsController foreman: authorization flaw in the Foreman::Controller::UserAware handling used by Api::V2::SshKeysController pulpcore: pulpcore: file:// scheme allowlist bypass in content upload file_url field enables arbitrary file read and Pulp Container registry signing key theft rubygem-foreman_ansible: Ansible inventory API ignores view_hosts permission filters, exposes hidden parameters rubygem-foreman_remote_execution: Job output readable without object-level view_job_invocations check pyjwt: pyjwt: Verification key substitution via unvalidated JWKS redirects pyjwt: PyJWT: Authentication bypass via improper public key validation pyjwt: pyjwt: Token forgery via improper Unicode byte-order mark handling pyjwt: pyjwt: Token forgery via acceptance of public JWK containers as HMAC secrets pulp-rpm: Distribution tree publish creates directories from .treeinfo ids candlepin: candlepin: broken…</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rhsa-2026:100120"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-61847</id>
    <title>UBUNTU-CVE-2026-61847</title>
    <updated>2026-11-16T16:54:53.112834+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>Crass is a Ruby CSS parser that'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 by recursively consuming the next token. An attacker-provided stylesheet containing a very large number of adjacent comments can cause excessive recursion and trigger a `SystemStackError`, denying service to the parsing application. Preserving comments avoids this recursive path. This issue is fixed in version 1.0.7.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-61847"/>
  </entry>
</feed>
