<?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 22:29:53 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-119202</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-119202</link>
      <description>&lt;p&gt;@hapi/content provides HTTP Content-* header parsing. From 3.0.6 until 6.0.3, Content.disposition() uses an unanchored parameter-name expression in a global regular-expression scan, causing repeated failed matching over the remaining input when a Content-Disposition parameter contains a long token without an equals sign. The resulting quadratic processing can block the Node.js event loop before route handlers or validation when @hapi/pez parses multipart/form-data headers, including unauthenticated hapi routes with payload.multipart enabled, and also affects applications that pass untrusted headers directly to Content.disposition(). This issue is fixed in @hapi/content version 6.0.3.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;@hapi/content provides HTTP Content-* header parsing. From 3.0.6 until 6.0.3, Content.disposition() uses an unanchored parameter-name expression in a global regular-expression scan, causing repeated failed matching over the remaining input when a Content-Disposition parameter contains a long token without an equals sign. The resulting quadratic processing can block the Node.js event loop before route handlers or validation when @hapi/pez parses multipart/form-data headers, including unauthenticated hapi routes with payload.multipart enabled, and also affects applications that pass untrusted headers directly to Content.disposition(). This issue is fixed in @hapi/content version 6.0.3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-119202</guid>
    </item>
    <item>
      <title>GHSA-8494-f6mr-cjpv — @hapi/content: quadratic-time parsing of Content-Disposition parameters allows denial of service</title>
      <link>https://db.gcve.eu/vuln/ghsa-8494-f6mr-cjpv</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @hapi/content, npm: content&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;`Content.disposition()` takes quadratic time when a `Content-Disposition` parameter contains a long token without `=`. One unauthenticated multipart request can block the Node.js event loop for several minutes.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;`Content.disposition()` reads the parameters with a global regular expression in `String.prototype.replace()`:&lt;/p&gt;
&lt;p&gt;```js
/([^\=\*\s]+)(\*)?\s*\=\s*(?:([^;&amp;#39;&amp;#34;\s]+\&amp;#39;[\w-]*\&amp;#39;[^;\s]+)|(?:\&amp;#34;([^&amp;#34;]*)\&amp;#34;)|([^;\s]*))/g
```&lt;/p&gt;
&lt;p&gt;The parameter name part `([^\=\*\s]+)` has no anchor. When a run of name characters has no `=` after it, the match attempt reads the full run and fails. The global scan then starts again at the next character and reads the remaining run again. The total time is proportional to the square of the run length.&lt;/p&gt;
&lt;p&gt;`@hapi/pez` calls `Content.disposition()` on the header of every part in a `multipart/form-data` body. In hapi, this occurs on each route with `payload.multipart` enabled, before the route handler and before any validation. The only size limit is the route `payload.maxBytes`, which is 1 MB by default.&lt;/p&gt;
&lt;p&gt;The fix adds an alternative that matches the full run of name characters when no `=` follows it. The scan then continues after the run, and the callback ignores this match. A match attempt that starts later in the same run always fails in the same way, so the parse result does not change. The parse time is now linear.&lt;/p&gt;
&lt;p&gt;```js
/([^\=\*\s]+)(\*)?\s*\=\s*(?:([^;&amp;#39;&amp;#34;\s]+\&amp;#39;[\w-]*\&amp;#39;[^;\s]+)|(?:\&amp;#34;([^&amp;#34;]*)\&amp;#34;)|([^;\s]*))|[^\=\*\s]+/g
```&lt;/p&gt;
&lt;p&gt;Every re…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @hapi/content, npm: content&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;`Content.disposition()` takes quadratic time when a `Content-Disposition` parameter contains a long token without `=`. One unauthenticated multipart request can block the Node.js event loop for several minutes.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;`Content.disposition()` reads the parameters with a global regular expression in `String.prototype.replace()`:&lt;/p&gt;
&lt;p&gt;```js
/([^\=\*\s]+)(\*)?\s*\=\s*(?:([^;&amp;#39;&amp;#34;\s]+\&amp;#39;[\w-]*\&amp;#39;[^;\s]+)|(?:\&amp;#34;([^&amp;#34;]*)\&amp;#34;)|([^;\s]*))/g
```&lt;/p&gt;
&lt;p&gt;The parameter name part `([^\=\*\s]+)` has no anchor. When a run of name characters has no `=` after it, the match attempt reads the full run and fails. The global scan then starts again at the next character and reads the remaining run again. The total time is proportional to the square of the run length.&lt;/p&gt;
&lt;p&gt;`@hapi/pez` calls `Content.disposition()` on the header of every part in a `multipart/form-data` body. In hapi, this occurs on each route with `payload.multipart` enabled, before the route handler and before any validation. The only size limit is the route `payload.maxBytes`, which is 1 MB by default.&lt;/p&gt;
&lt;p&gt;The fix adds an alternative that matches the full run of name characters when no `=` follows it. The scan then continues after the run, and the callback ignores this match. A match attempt that starts later in the same run always fails in the same way, so the parse result does not change. The parse time is now linear.&lt;/p&gt;
&lt;p&gt;```js
/([^\=\*\s]+)(\*)?\s*\=\s*(?:([^;&amp;#39;&amp;#34;\s]+\&amp;#39;[\w-]*\&amp;#39;[^;\s]+)|(?:\&amp;#34;([^&amp;#34;]*)\&amp;#34;)|([^;\s]*))|[^\=\*\s]+/g
```&lt;/p&gt;
&lt;p&gt;Every re…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-8494-f6mr-cjpv</guid>
    </item>
  </channel>
</rss>
