<?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://cve.radiocsirt.org</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, 02 Oct 2026 23:57:03 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-42874 — Microdot: HTTP response splitting in Response.set_cookie()</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-42874</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; miguelgrinberg microdot&lt;/p&gt;
&lt;p&gt;Microdot is a minimalistic Python web framework. Prior to 2.6.1, the Response.set_cookie() method does not sanitize its string arguments, and in particular will not detect the presence of the \r\n sequence in them. This can be a potential source of header injection attacks. For a header injection attack through this issue to be possible, an attacker must first infiltrate the client (for example through an independent XSS attack), so that it can send malicious information that is destined to be stored in a cookie by the server on behalf of the victim. An attacker that infiltrates one client can only orchestrate a header injection attack for that client, all other clients that were not infiltrated are safe. This vulnerability is fixed in 2.6.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; miguelgrinberg microdot&lt;/p&gt;
&lt;p&gt;Microdot is a minimalistic Python web framework. Prior to 2.6.1, the Response.set_cookie() method does not sanitize its string arguments, and in particular will not detect the presence of the \r\n sequence in them. This can be a potential source of header injection attacks. For a header injection attack through this issue to be possible, an attacker must first infiltrate the client (for example through an independent XSS attack), so that it can send malicious information that is destined to be stored in a cookie by the server on behalf of the victim. An attacker that infiltrates one client can only orchestrate a header injection attack for that client, all other clients that were not infiltrated are safe. This vulnerability is fixed in 2.6.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-42874</guid>
    </item>
    <item>
      <title>GHSA-7wc8-wvc4-m498 — Microdot has HTTP response splitting in Response.set_cookie()</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7wc8-wvc4-m498</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: microdot&lt;/p&gt;
&lt;p&gt;### Impact
The `Response.set_cookie()` method does not sanitize its string arguments, and in particular will not detect the presence of the `\r\n` sequence in them. This can be a potential source of header injection attacks.&lt;/p&gt;
&lt;p&gt;For a header injection attack through this issue to be possible, an attacker must first infiltrate the client (for example through an independent XSS attack), so that it can send malicious information that is destined to be stored in a cookie by the server on behalf of the victim. An attacker that infiltrates one client can only orchestrate a header injection attack for that client, all other clients that were not infiltrated are safe.&lt;/p&gt;
&lt;p&gt;### Patches
Upgrade to version 2.6.1.&lt;/p&gt;
&lt;p&gt;### Workarounds
Do not pass untrusted data to the `Response.set_cookie()` method.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: microdot&lt;/p&gt;
&lt;p&gt;### Impact
The `Response.set_cookie()` method does not sanitize its string arguments, and in particular will not detect the presence of the `\r\n` sequence in them. This can be a potential source of header injection attacks.&lt;/p&gt;
&lt;p&gt;For a header injection attack through this issue to be possible, an attacker must first infiltrate the client (for example through an independent XSS attack), so that it can send malicious information that is destined to be stored in a cookie by the server on behalf of the victim. An attacker that infiltrates one client can only orchestrate a header injection attack for that client, all other clients that were not infiltrated are safe.&lt;/p&gt;
&lt;p&gt;### Patches
Upgrade to version 2.6.1.&lt;/p&gt;
&lt;p&gt;### Workarounds
Do not pass untrusted data to the `Response.set_cookie()` method.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7wc8-wvc4-m498</guid>
    </item>
  </channel>
</rss>
