https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 30 Sep 2026 10:28:48 +0000 https://db.gcve.eu/vuln/cleanstart-2026-bz34895 <p><strong>Affected:</strong> CleanStart: npm</p> <p>ghsa-g8m3-5g58-fq7m affects multiple packages. This issue is resolved in later releases. See references for individual vulnerability details.</p> <p><strong>Affected:</strong> CleanStart: npm</p> <p>ghsa-g8m3-5g58-fq7m affects multiple packages. This issue is resolved in later releases. See references for individual vulnerability details.</p> https://db.gcve.eu/vuln/cleanstart-2026-bz34895 https://db.gcve.eu/vuln/cve-2026-11525 <p><strong>Affected:</strong> undici</p> <p>Impact: When undici parses a Set-Cookie header, it accepts any SameSite attribute value that contains Strict, Lax, or None as a substring, rather than the case-insensitive exact match specified by RFC 6265. Non-spec values are silently mapped to one of the three standard tokens. For example, SameSite=NoneOfYourBusiness is parsed as None (the most permissive setting), and SameSite=StrictLax is parsed as Lax (a downgrade from Strict).</p> <p>Affected applications are those that consume Set-Cookie headers from server responses (for example via undici&#39;s fetch or proxy code paths) and then forward or rely on the parsed sameSite attribute. A malicious or non-compliant server can coerce the consumer&#39;s view of a cookie&#39;s SameSite policy to a weaker value, silently degrading the SameSite enforcement the cookie is supposed to provide.</p> <p>This was introduced in undici 5.15.0 when the cookies feature was added.</p> <p>Patches: Upgrade to undici v6.26.0, v7.28.0 or v8.5.0.</p> <p>Workarounds: After parsing a Set-Cookie header, validate that the resulting sameSite attribute is one of &#39;Strict&#39;, &#39;Lax&#39;, or &#39;None&#39; (exact, case-insensitive) before forwarding or relying on it.</p> <p><strong>Affected:</strong> undici</p> <p>Impact: When undici parses a Set-Cookie header, it accepts any SameSite attribute value that contains Strict, Lax, or None as a substring, rather than the case-insensitive exact match specified by RFC 6265. Non-spec values are silently mapped to one of the three standard tokens. For example, SameSite=NoneOfYourBusiness is parsed as None (the most permissive setting), and SameSite=StrictLax is parsed as Lax (a downgrade from Strict).</p> <p>Affected applications are those that consume Set-Cookie headers from server responses (for example via undici&#39;s fetch or proxy code paths) and then forward or rely on the parsed sameSite attribute. A malicious or non-compliant server can coerce the consumer&#39;s view of a cookie&#39;s SameSite policy to a weaker value, silently degrading the SameSite enforcement the cookie is supposed to provide.</p> <p>This was introduced in undici 5.15.0 when the cookies feature was added.</p> <p>Patches: Upgrade to undici v6.26.0, v7.28.0 or v8.5.0.</p> <p>Workarounds: After parsing a Set-Cookie header, validate that the resulting sameSite attribute is one of &#39;Strict&#39;, &#39;Lax&#39;, or &#39;None&#39; (exact, case-insensitive) before forwarding or relying on it.</p> https://db.gcve.eu/vuln/cve-2026-11525