<?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>Wed, 30 Sep 2026 23:55:43 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-69214</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-69214</link>
      <description>&lt;p&gt;Http4s is a Scala interface for HTTP services. Prior to 0.23.35 and 1.0.0-M47, The CookieJar client middleware stores a response cookie’s Domain attribute without checking that it domain-matches the host that supplied the cookie or rejecting public suffixes. A malicious or compromised server contacted through the same CookieJar can plant a cookie for another domain, and the jar later sends that cookie to the victim domain, enabling session fixation or overwriting security-sensitive cookies. The patch validates the Set-Cookie domain against the response origin, although public-suffix rejection remains unimplemented. This issue is fixed in versions 0.23.35 and 1.0.0-M47.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Http4s is a Scala interface for HTTP services. Prior to 0.23.35 and 1.0.0-M47, The CookieJar client middleware stores a response cookie’s Domain attribute without checking that it domain-matches the host that supplied the cookie or rejecting public suffixes. A malicious or compromised server contacted through the same CookieJar can plant a cookie for another domain, and the jar later sends that cookie to the victim domain, enabling session fixation or overwriting security-sensitive cookies. The patch validates the Set-Cookie domain against the response origin, although public-suffix rejection remains unimplemented. This issue is fixed in versions 0.23.35 and 1.0.0-M47.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-69214</guid>
    </item>
    <item>
      <title>GHSA-wv64-j4fq-5f9x — Http4s: CookieJar middleware accepts arbitrary Set-Cookie domain</title>
      <link>https://db.gcve.eu/vuln/ghsa-wv64-j4fq-5f9x</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.http4s:http4s-client_2.12, Maven: org.http4s:http4s-client_2.13, Maven: org.http4s:http4s-client_3&lt;/p&gt;
&lt;p&gt;When processing a `Set-Cookie` from a response, the `CookieJar` client middleware trusts the server-supplied `Domain` attribute verbatim, with no check that it domain-matches the host that sent the cookie (RFC6265 §5.3 step 6) and no public suffix check.  A malicious or compromised server can therefore plant a cookie for any domain in the cookie jar, which is subsequently set on the client&amp;#39;s next request to that victim domain, enabling session fixation or overwriting security-relevant cookies.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Session fixation and overwrite of security-relevant cookies for arbitrary domains contacted by the same wrapped client.&lt;/p&gt;
&lt;p&gt;## Preconditions&lt;/p&gt;
&lt;p&gt;- Application uses the `CookieJar` client middleware.
- Application contacts an attacker-controlled (or compromised) server using the same jar it uses for trusted hosts.&lt;/p&gt;
&lt;p&gt;## Workarounds&lt;/p&gt;
&lt;p&gt;- Do not share a `CookieJar` across trusted and untrusted targets.&lt;/p&gt;
&lt;p&gt;## Note&lt;/p&gt;
&lt;p&gt;This middleware still does not implement public suffix rejection.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.http4s:http4s-client_2.12, Maven: org.http4s:http4s-client_2.13, Maven: org.http4s:http4s-client_3&lt;/p&gt;
&lt;p&gt;When processing a `Set-Cookie` from a response, the `CookieJar` client middleware trusts the server-supplied `Domain` attribute verbatim, with no check that it domain-matches the host that sent the cookie (RFC6265 §5.3 step 6) and no public suffix check.  A malicious or compromised server can therefore plant a cookie for any domain in the cookie jar, which is subsequently set on the client&amp;#39;s next request to that victim domain, enabling session fixation or overwriting security-relevant cookies.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Session fixation and overwrite of security-relevant cookies for arbitrary domains contacted by the same wrapped client.&lt;/p&gt;
&lt;p&gt;## Preconditions&lt;/p&gt;
&lt;p&gt;- Application uses the `CookieJar` client middleware.
- Application contacts an attacker-controlled (or compromised) server using the same jar it uses for trusted hosts.&lt;/p&gt;
&lt;p&gt;## Workarounds&lt;/p&gt;
&lt;p&gt;- Do not share a `CookieJar` across trusted and untrusted targets.&lt;/p&gt;
&lt;p&gt;## Note&lt;/p&gt;
&lt;p&gt;This middleware still does not implement public suffix rejection.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-wv64-j4fq-5f9x</guid>
    </item>
  </channel>
</rss>
