<?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>Sat, 31 Oct 2026 23:19:28 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-118772</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-118772</link>
      <description>&lt;p&gt;joi is a schema description language and data validator for JavaScript. From 17.1.1 until 17.13.9 and 18.3.1, the Joi.string().email({ multiple: true }) rule uses a separator regular expression whose leading whitespace quantifier is retried at every position in a long whitespace run that contains no separator, causing quadratic work during String.prototype.split. The behavior applies to the default separator and every custom separator. Applications that validate attacker-controlled values with the multiple option and no effective prior length limit can have the Node.js event loop blocked for seconds by one request, preventing other work. A .max() rule is not sufficient when abortEarly: false allows the email rule to run after the maximum-length check fails. This vulnerability is fixed in versions 17.13.9 and 18.3.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;joi is a schema description language and data validator for JavaScript. From 17.1.1 until 17.13.9 and 18.3.1, the Joi.string().email({ multiple: true }) rule uses a separator regular expression whose leading whitespace quantifier is retried at every position in a long whitespace run that contains no separator, causing quadratic work during String.prototype.split. The behavior applies to the default separator and every custom separator. Applications that validate attacker-controlled values with the multiple option and no effective prior length limit can have the Node.js event loop blocked for seconds by one request, preventing other work. A .max() rule is not sufficient when abortEarly: false allows the email rule to run after the maximum-length check fails. This vulnerability is fixed in versions 17.13.9 and 18.3.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-118772</guid>
    </item>
    <item>
      <title>GHSA-4528-x5fx-h6hg — joi: quadratic-time split in `string().email({ multiple: true })` allows denial of service</title>
      <link>https://db.gcve.eu/vuln/ghsa-4528-x5fx-h6hg</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: joi, npm: @hapi/joi&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;`Joi.string().email({ multiple: true })` takes quadratic time to split a value that contains a long run of whitespace. One request with 100 KB of spaces blocks the Node.js event loop for several seconds, which causes a denial of service.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;When the `multiple` option is set, the `email` rule splits the value into addresses with a regular expression that removes whitespace on each side of the separator:&lt;/p&gt;
&lt;p&gt;```js
const regex = new RegExp(`\\s*[${options.separator ? escapeRegex(options.separator) : &amp;#39;,&amp;#39;}]\\s*`);
// ...
const emails = options.multiple ? value.split(regex) : [value];
```&lt;/p&gt;
&lt;p&gt;`String.prototype.split` tries a match at each position of the value. At each position inside a whitespace run, the leading `\s*` reads the rest of the run, does not find a separator, and backtracks through all of it. A run of `n` whitespace characters without a separator therefore costs `n²` steps. This applies to the default separator and to all custom `separator` values.&lt;/p&gt;
&lt;p&gt;The fix lets the leading whitespace match start only at the beginning of a whitespace run, so the split is linear:&lt;/p&gt;
&lt;p&gt;```js
const regex = new RegExp(`(?:(?&amp;lt;!\\s)\\s+)?[${options.separator ? escapeRegex(options.separator) : &amp;#39;,&amp;#39;}]\\s*`);
```&lt;/p&gt;
&lt;p&gt;The split results do not change. The regular expression is now built only when `multiple` is set.&lt;/p&gt;
&lt;p&gt;Every `joi` release from `17.1.1` up to and including `17.13.8`, and from `18.0.0` up to and including `18.3.0`, is affected. Every `@hapi/joi` release from `16.0.0` is af…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: joi, npm: @hapi/joi&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;`Joi.string().email({ multiple: true })` takes quadratic time to split a value that contains a long run of whitespace. One request with 100 KB of spaces blocks the Node.js event loop for several seconds, which causes a denial of service.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;When the `multiple` option is set, the `email` rule splits the value into addresses with a regular expression that removes whitespace on each side of the separator:&lt;/p&gt;
&lt;p&gt;```js
const regex = new RegExp(`\\s*[${options.separator ? escapeRegex(options.separator) : &amp;#39;,&amp;#39;}]\\s*`);
// ...
const emails = options.multiple ? value.split(regex) : [value];
```&lt;/p&gt;
&lt;p&gt;`String.prototype.split` tries a match at each position of the value. At each position inside a whitespace run, the leading `\s*` reads the rest of the run, does not find a separator, and backtracks through all of it. A run of `n` whitespace characters without a separator therefore costs `n²` steps. This applies to the default separator and to all custom `separator` values.&lt;/p&gt;
&lt;p&gt;The fix lets the leading whitespace match start only at the beginning of a whitespace run, so the split is linear:&lt;/p&gt;
&lt;p&gt;```js
const regex = new RegExp(`(?:(?&amp;lt;!\\s)\\s+)?[${options.separator ? escapeRegex(options.separator) : &amp;#39;,&amp;#39;}]\\s*`);
```&lt;/p&gt;
&lt;p&gt;The split results do not change. The regular expression is now built only when `multiple` is set.&lt;/p&gt;
&lt;p&gt;Every `joi` release from `17.1.1` up to and including `17.13.8`, and from `18.0.0` up to and including `18.3.0`, is affected. Every `@hapi/joi` release from `16.0.0` is af…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-4528-x5fx-h6hg</guid>
    </item>
  </channel>
</rss>
