<?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>Wed, 30 Sep 2026 02:50:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-9086 — Out of bounds read for cookie path</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-9086</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; curl, Siemens RUGGEDCOM RST2428P, Siemens SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family, Siemens SCALANCE XCH328, Siemens SCALANCE XCM324, Siemens SCALANCE XCM328, Siemens SCALANCE XCM332, Siemens SCALANCE XRH334 (24 V DC, 8xFO, CC), Siemens SCALANCE XRM334 (230 V AC, 12xFO), Siemens SCALANCE XRM334 (230 V AC, 8xFO) and 7 more&lt;/p&gt;
&lt;p&gt;1. A cookie is set using the `secure` keyword for `https://target`
2. curl is redirected to or otherwise made to speak with `http://target` (same
   hostname, but using clear text HTTP) using the same cookie set
3. The same cookie name is set - but with only a slash as path (`path=&amp;#34;/&amp;#34;`).
   Since this site is not secure, the cookie *should* be ignored.
4. A bug in the path comparison logic makes curl read outside a heap buffer
   boundary&lt;/p&gt;
&lt;p&gt;The bug either causes a crash or it potentially makes the comparison come to
the wrong conclusion and lets the clear-text site override the contents of the
secure cookie, contrary to expectations and depending on the memory contents
immediately following the single-byte allocation that holds the path.&lt;/p&gt;
&lt;p&gt;The presumed and correct behavior would be to plainly ignore the second set of
the cookie since it was already set as secure on a secure host so overriding
it on an insecure host should not be okay.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; curl, Siemens RUGGEDCOM RST2428P, Siemens SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family, Siemens SCALANCE XCH328, Siemens SCALANCE XCM324, Siemens SCALANCE XCM328, Siemens SCALANCE XCM332, Siemens SCALANCE XRH334 (24 V DC, 8xFO, CC), Siemens SCALANCE XRM334 (230 V AC, 12xFO), Siemens SCALANCE XRM334 (230 V AC, 8xFO) and 7 more&lt;/p&gt;
&lt;p&gt;1. A cookie is set using the `secure` keyword for `https://target`
2. curl is redirected to or otherwise made to speak with `http://target` (same
   hostname, but using clear text HTTP) using the same cookie set
3. The same cookie name is set - but with only a slash as path (`path=&amp;#34;/&amp;#34;`).
   Since this site is not secure, the cookie *should* be ignored.
4. A bug in the path comparison logic makes curl read outside a heap buffer
   boundary&lt;/p&gt;
&lt;p&gt;The bug either causes a crash or it potentially makes the comparison come to
the wrong conclusion and lets the clear-text site override the contents of the
secure cookie, contrary to expectations and depending on the memory contents
immediately following the single-byte allocation that holds the path.&lt;/p&gt;
&lt;p&gt;The presumed and correct behavior would be to plainly ignore the second set of
the cookie since it was already set as secure on a secure host so overriding
it on an insecure host should not be okay.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-9086</guid>
    </item>
  </channel>
</rss>
