<?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, 12 Oct 2026 22:50:18 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-32657</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-32657</link>
      <description>EUVD-2026-32657</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-32657</guid>
    </item>
    <item>
      <title>fkie_cve-2021-43805</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-43805</link>
      <description>&lt;p&gt;Solidus is a free, open-source ecommerce platform built on Rails. Versions of Solidus prior to 3.1.4, 3.0.4, and 2.11.13 have a denial of service vulnerability that could be exploited during a guest checkout. The regular expression used to validate a guest order&amp;#39;s email was subject to exponential backtracking through a fragment like `a.a.` Versions 3.1.4, 3.0.4, and 2.11.13 have been patched to use a different regular expression. The maintainers added a check for email addresses that are no longer valid that will print information about any affected orders that exist. If a prompt upgrade is not an option, a workaround is available. It is possible to edit the file `config/application.rb` manually (with code provided by the maintainers in the GitHub Security Advisory) to check email validity.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Solidus is a free, open-source ecommerce platform built on Rails. Versions of Solidus prior to 3.1.4, 3.0.4, and 2.11.13 have a denial of service vulnerability that could be exploited during a guest checkout. The regular expression used to validate a guest order&amp;#39;s email was subject to exponential backtracking through a fragment like `a.a.` Versions 3.1.4, 3.0.4, and 2.11.13 have been patched to use a different regular expression. The maintainers added a check for email addresses that are no longer valid that will print information about any affected orders that exist. If a prompt upgrade is not an option, a workaround is available. It is possible to edit the file `config/application.rb` manually (with code provided by the maintainers in the GitHub Security Advisory) to check email validity.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-43805</guid>
    </item>
    <item>
      <title>GHSA-qxmr-qxh6-2cc9 — ReDos vulnerability on guest checkout email validation</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qxmr-qxh6-2cc9</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: solidus_core&lt;/p&gt;
&lt;p&gt;### Impact
Denial of service vulnerability that could be exploited during a guest checkout. The regular expression used to validate a guest order&amp;#39;s email was subject to exponential backtracking through a fragment like `a.a.`.&lt;/p&gt;
&lt;p&gt;Before the patch, it can be reproduced in the console like this:&lt;/p&gt;
&lt;p&gt;```ruby
irb(main)&amp;gt; Spree::EmailValidator::EMAIL_REGEXP.match &amp;#34;a@a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.@&amp;#34;
processing time: 54.293660s
=&amp;gt; nil
```&lt;/p&gt;
&lt;p&gt;To reproduce in the browser, fill in the &amp;#34;Customer Email&amp;#34; field with that fake email address during a guest checkout. Before that, you should open the browser dev tools and change the `type` attribute for that field from `email` to `text`. After entering a fake address and pressing the &amp;#34;Save &amp;amp; Continue&amp;#34; button, the browser will take a long term to perform the request before showing an error message for the invalid address. Eventually, making the email string even longer could lead to the exhaustion of server resources.&lt;/p&gt;
&lt;p&gt;### Patches
Versions 3.1.4, 3.0.4, and 2.11.13 have been patched to use a different regular expression.&lt;/p&gt;
&lt;p&gt;There&amp;#39;s an improbable chance that some orders in your system end up having associated an email address that is no longer valid. We&amp;#39;ve added a task to check precisely that:&lt;/p&gt;
&lt;p&gt;```bash
bin/rails solidus:check_orders_with_invalid_email
```&lt;/p&gt;
&lt;p&gt;The above will print information for every affected order if any.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;If a prompt upgrade is not an option, please, add the following to `config/application.…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: solidus_core&lt;/p&gt;
&lt;p&gt;### Impact
Denial of service vulnerability that could be exploited during a guest checkout. The regular expression used to validate a guest order&amp;#39;s email was subject to exponential backtracking through a fragment like `a.a.`.&lt;/p&gt;
&lt;p&gt;Before the patch, it can be reproduced in the console like this:&lt;/p&gt;
&lt;p&gt;```ruby
irb(main)&amp;gt; Spree::EmailValidator::EMAIL_REGEXP.match &amp;#34;a@a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.@&amp;#34;
processing time: 54.293660s
=&amp;gt; nil
```&lt;/p&gt;
&lt;p&gt;To reproduce in the browser, fill in the &amp;#34;Customer Email&amp;#34; field with that fake email address during a guest checkout. Before that, you should open the browser dev tools and change the `type` attribute for that field from `email` to `text`. After entering a fake address and pressing the &amp;#34;Save &amp;amp; Continue&amp;#34; button, the browser will take a long term to perform the request before showing an error message for the invalid address. Eventually, making the email string even longer could lead to the exhaustion of server resources.&lt;/p&gt;
&lt;p&gt;### Patches
Versions 3.1.4, 3.0.4, and 2.11.13 have been patched to use a different regular expression.&lt;/p&gt;
&lt;p&gt;There&amp;#39;s an improbable chance that some orders in your system end up having associated an email address that is no longer valid. We&amp;#39;ve added a task to check precisely that:&lt;/p&gt;
&lt;p&gt;```bash
bin/rails solidus:check_orders_with_invalid_email
```&lt;/p&gt;
&lt;p&gt;The above will print information for every affected order if any.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;If a prompt upgrade is not an option, please, add the following to `config/application.…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qxmr-qxh6-2cc9</guid>
    </item>
    <item>
      <title>gsd-2021-43805</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-43805</link>
      <description>gsd-2021-43805</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-43805</guid>
    </item>
  </channel>
</rss>
