<?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>Mon, 05 Oct 2026 16:32:52 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-323548</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-323548</link>
      <description>EUVD-2026-323548</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-323548</guid>
    </item>
    <item>
      <title>fkie_cve-2026-9658</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-9658</link>
      <description>&lt;p&gt;Plack::Middleware::Security::Common versions before 0.13.1 for Perl did not block header injections in request paths.&lt;/p&gt;
&lt;p&gt;The header injection rule was ineffective at blocking header injections in the request paths unless they were double-encoded, for example,&lt;/p&gt;
&lt;p&gt;GET /path\r\nHTTP/1.1\r\nHost: secret.example.com&lt;/p&gt;
&lt;p&gt;Note that it is unclear whether request paths with CRLF followed by additional headers would be blocked by reverse proxies, or how they would be processed by Plack-based servers.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Plack::Middleware::Security::Common versions before 0.13.1 for Perl did not block header injections in request paths.&lt;/p&gt;
&lt;p&gt;The header injection rule was ineffective at blocking header injections in the request paths unless they were double-encoded, for example,&lt;/p&gt;
&lt;p&gt;GET /path\r\nHTTP/1.1\r\nHost: secret.example.com&lt;/p&gt;
&lt;p&gt;Note that it is unclear whether request paths with CRLF followed by additional headers would be blocked by reverse proxies, or how they would be processed by Plack-based servers.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-9658</guid>
    </item>
    <item>
      <title>GHSA-xcq6-chp9-g954</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-xcq6-chp9-g954</link>
      <description>&lt;p&gt;Plack::Middleware::Security::Common versions before 0.13.1 for Perl did not block header injections in request paths.&lt;/p&gt;
&lt;p&gt;The header injection rule was ineffective at blocking header injections in the request paths unless they were double-encoded, for example,&lt;/p&gt;
&lt;p&gt;GET /path\r\nHTTP/1.1\r\nHost: secret.example.com&lt;/p&gt;
&lt;p&gt;Note that it is unclear whether request paths with CRLF followed by additional headers would be blocked by reverse proxies, or how they would be processed by Plack-based servers.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Plack::Middleware::Security::Common versions before 0.13.1 for Perl did not block header injections in request paths.&lt;/p&gt;
&lt;p&gt;The header injection rule was ineffective at blocking header injections in the request paths unless they were double-encoded, for example,&lt;/p&gt;
&lt;p&gt;GET /path\r\nHTTP/1.1\r\nHost: secret.example.com&lt;/p&gt;
&lt;p&gt;Note that it is unclear whether request paths with CRLF followed by additional headers would be blocked by reverse proxies, or how they would be processed by Plack-based servers.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-xcq6-chp9-g954</guid>
    </item>
  </channel>
</rss>
