<?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://db.gcve.eu</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>Tue, 29 Sep 2026 17:40:17 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-92599 — Joi before 17.13.7 and 18.2.6 ReDoS via isoDate</title>
      <link>https://db.gcve.eu/vuln/cve-2026-92599</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; hapijs joi&lt;/p&gt;
&lt;p&gt;joi (npm package `joi`, hapi.js) versions &amp;gt;=17.2.0 &amp;lt;17.13.7 and &amp;gt;=18.0.0 &amp;lt;18.2.6 are vulnerable to regular expression denial of service in the `Joi.string().isoDate()` validation rule. One of the regular expressions the rule applies to the input is unanchored, so a valid ISO date followed by a long run of fractional-second digits causes the regex engine to restart its search from every position in the string, yielding time proportional to the square of the input length (about 1.4 s for 64 KB of digits and about 22 s for 256 KB). A remote attacker who can supply a string to an isoDate validation can stall the application with a single request. Fixed in 17.13.7 and 18.2.6; as a workaround, cap the length of the string before it reaches joi.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; hapijs joi&lt;/p&gt;
&lt;p&gt;joi (npm package `joi`, hapi.js) versions &amp;gt;=17.2.0 &amp;lt;17.13.7 and &amp;gt;=18.0.0 &amp;lt;18.2.6 are vulnerable to regular expression denial of service in the `Joi.string().isoDate()` validation rule. One of the regular expressions the rule applies to the input is unanchored, so a valid ISO date followed by a long run of fractional-second digits causes the regex engine to restart its search from every position in the string, yielding time proportional to the square of the input length (about 1.4 s for 64 KB of digits and about 22 s for 256 KB). A remote attacker who can supply a string to an isoDate validation can stall the application with a single request. Fixed in 17.13.7 and 18.2.6; as a workaround, cap the length of the string before it reaches joi.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-92599</guid>
    </item>
  </channel>
</rss>
