<?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://vulnerability.circl.lu</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>Sun, 11 Oct 2026 17:09:58 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-107228</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-107228</link>
      <description>&lt;p&gt;The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. From 2.1.0 until 3.0.14, the enabled-by-default cookie store replaces a Cookie header explicitly supplied through setHeader or addHeader whenever the store contributes any cookie for the origin. In a shared client, stored cookies originating from one user can replace a different user&amp;#39;s request cookie, causing the request to execute under the wrong session. This bypasses the earlier CVE-2024-53990 remediation, which covered cookies supplied through addCookie but not a directly supplied header. This issue is fixed in version 3.0.14.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. From 2.1.0 until 3.0.14, the enabled-by-default cookie store replaces a Cookie header explicitly supplied through setHeader or addHeader whenever the store contributes any cookie for the origin. In a shared client, stored cookies originating from one user can replace a different user&amp;#39;s request cookie, causing the request to execute under the wrong session. This bypasses the earlier CVE-2024-53990 remediation, which covered cookies supplied through addCookie but not a directly supplied header. This issue is fixed in version 3.0.14.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-107228</guid>
    </item>
    <item>
      <title>GHSA-2jwh-9rmr-j4xf — AsyncHttpClient CookieStore Silently Overrides Caller's Explicit Cookie Header via setHeader (Bypass of CVE-2024-53990…</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-2jwh-9rmr-j4xf</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.asynchttpclient:async-http-client&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;With the cookie store enabled, which is the default, a `Cookie` header that the caller sets on a request with `setHeader` or `addHeader` is thrown away whenever the store holds any cookie for the request&amp;#39;s origin: the request&amp;#39;s cookie list is written into that header afterwards and replaces it. CVE-2024-53990 fixed the same problem for cookies added with `addCookie`, but that fix works on the cookie list, and a header set directly never reaches it.&lt;/p&gt;
&lt;p&gt;This is not limited to a cookie of the same name. A store cookie of any name erases the caller&amp;#39;s header, so a request meant to carry the caller&amp;#39;s session cookie goes out with only the store&amp;#39;s cookies, and where the store has a cookie of the caller&amp;#39;s name, the store&amp;#39;s value is sent instead.&lt;/p&gt;
&lt;p&gt;It matters most where one client acts for several users. An application that puts each user&amp;#39;s session on the request itself, and shares one client and its default cookie store, sends one user&amp;#39;s request with a session cookie the store took from a response to another user. The request runs as that other user, so a user of such an application can have their request served under someone else&amp;#39;s session, or someone else&amp;#39;s under theirs.&lt;/p&gt;
&lt;p&gt;### Affected versions&lt;/p&gt;
&lt;p&gt;* 3.x: up to and including 3.0.13
* 2.x: from 2.1.0 up to and including 2.16.1&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed in 3.0.14. The store&amp;#39;s cookies are added to a caller&amp;#39;s `Cookie` header instead of replacing it, and where both name the same cookie the caller&amp;#39;s is kept. The caller&amp;#39;s text is kept as w…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.asynchttpclient:async-http-client&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;With the cookie store enabled, which is the default, a `Cookie` header that the caller sets on a request with `setHeader` or `addHeader` is thrown away whenever the store holds any cookie for the request&amp;#39;s origin: the request&amp;#39;s cookie list is written into that header afterwards and replaces it. CVE-2024-53990 fixed the same problem for cookies added with `addCookie`, but that fix works on the cookie list, and a header set directly never reaches it.&lt;/p&gt;
&lt;p&gt;This is not limited to a cookie of the same name. A store cookie of any name erases the caller&amp;#39;s header, so a request meant to carry the caller&amp;#39;s session cookie goes out with only the store&amp;#39;s cookies, and where the store has a cookie of the caller&amp;#39;s name, the store&amp;#39;s value is sent instead.&lt;/p&gt;
&lt;p&gt;It matters most where one client acts for several users. An application that puts each user&amp;#39;s session on the request itself, and shares one client and its default cookie store, sends one user&amp;#39;s request with a session cookie the store took from a response to another user. The request runs as that other user, so a user of such an application can have their request served under someone else&amp;#39;s session, or someone else&amp;#39;s under theirs.&lt;/p&gt;
&lt;p&gt;### Affected versions&lt;/p&gt;
&lt;p&gt;* 3.x: up to and including 3.0.13
* 2.x: from 2.1.0 up to and including 2.16.1&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed in 3.0.14. The store&amp;#39;s cookies are added to a caller&amp;#39;s `Cookie` header instead of replacing it, and where both name the same cookie the caller&amp;#39;s is kept. The caller&amp;#39;s text is kept as w…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-2jwh-9rmr-j4xf</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-107228</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-107228</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: async-http-client, Ubuntu:16.04:LTS: async-http-client, Ubuntu:18.04:LTS: async-http-client, Ubuntu:Pro:20.04:LTS: async-http-client, Ubuntu:22.04:LTS: async-http-client, Ubuntu:24.04:LTS: async-http-client, Ubuntu:26.04:LTS: async-http-client&lt;/p&gt;
&lt;p&gt;The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. From 2.1.0 until 3.0.14, the enabled-by-default cookie store replaces a Cookie header explicitly supplied through setHeader or addHeader whenever the store contributes any cookie for the origin. In a shared client, stored cookies originating from one user can replace a different user&amp;#39;s request cookie, causing the request to execute under the wrong session. This bypasses the earlier CVE-2024-53990 remediation, which covered cookies supplied through addCookie but not a directly supplied header. This issue is fixed in version 3.0.14.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: async-http-client, Ubuntu:16.04:LTS: async-http-client, Ubuntu:18.04:LTS: async-http-client, Ubuntu:Pro:20.04:LTS: async-http-client, Ubuntu:22.04:LTS: async-http-client, Ubuntu:24.04:LTS: async-http-client, Ubuntu:26.04:LTS: async-http-client&lt;/p&gt;
&lt;p&gt;The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. From 2.1.0 until 3.0.14, the enabled-by-default cookie store replaces a Cookie header explicitly supplied through setHeader or addHeader whenever the store contributes any cookie for the origin. In a shared client, stored cookies originating from one user can replace a different user&amp;#39;s request cookie, causing the request to execute under the wrong session. This bypasses the earlier CVE-2024-53990 remediation, which covered cookies supplied through addCookie but not a directly supplied header. This issue is fixed in version 3.0.14.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-107228</guid>
    </item>
  </channel>
</rss>
