<?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>Fri, 06 Nov 2026 01:07:44 +0000</lastBuildDate>
    <item>
      <title>GHSA-pxg6-pf52-xh8x — cookie accepts cookie name, path, and domain with out of bounds characters</title>
      <link>https://db.gcve.eu/vuln/ghsa-pxg6-pf52-xh8x</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: cookie&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;The cookie name could be used to set other fields of the cookie, resulting in an unexpected cookie value. For example, `serialize(&amp;#34;userName=&amp;lt;script&amp;gt;alert(&amp;#39;XSS3&amp;#39;)&amp;lt;/script&amp;gt;; Max-Age=2592000; a&amp;#34;, value)` would result in `&amp;#34;userName=&amp;lt;script&amp;gt;alert(&amp;#39;XSS3&amp;#39;)&amp;lt;/script&amp;gt;; Max-Age=2592000; a=test&amp;#34;`, setting `userName` cookie to `&amp;lt;script&amp;gt;` and ignoring `value`.&lt;/p&gt;
&lt;p&gt;A similar escape can be used for `path` and `domain`, which could be abused to alter other fields of the cookie.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Upgrade to 0.7.0, which updates the validation for `name`, `path`, and `domain`.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Avoid passing untrusted or arbitrary values for these fields, ensure they are set by the application instead of user input.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;* https://github.com/jshttp/cookie/pull/167&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: cookie&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;The cookie name could be used to set other fields of the cookie, resulting in an unexpected cookie value. For example, `serialize(&amp;#34;userName=&amp;lt;script&amp;gt;alert(&amp;#39;XSS3&amp;#39;)&amp;lt;/script&amp;gt;; Max-Age=2592000; a&amp;#34;, value)` would result in `&amp;#34;userName=&amp;lt;script&amp;gt;alert(&amp;#39;XSS3&amp;#39;)&amp;lt;/script&amp;gt;; Max-Age=2592000; a=test&amp;#34;`, setting `userName` cookie to `&amp;lt;script&amp;gt;` and ignoring `value`.&lt;/p&gt;
&lt;p&gt;A similar escape can be used for `path` and `domain`, which could be abused to alter other fields of the cookie.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Upgrade to 0.7.0, which updates the validation for `name`, `path`, and `domain`.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Avoid passing untrusted or arbitrary values for these fields, ensure they are set by the application instead of user input.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;* https://github.com/jshttp/cookie/pull/167&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-pxg6-pf52-xh8x</guid>
    </item>
  </channel>
</rss>
