<?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>Wed, 14 Oct 2026 15:13:30 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-211221</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-211221</link>
      <description>EUVD-2026-211221</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-211221</guid>
    </item>
    <item>
      <title>fkie_cve-2009-4488</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2009-4488</link>
      <description>&lt;p&gt;Varnish 2.0.6 writes data to a log file without sanitizing non-printable characters, which might allow remote attackers to modify a window&amp;#39;s title, or possibly execute arbitrary commands or overwrite files, via an HTTP request containing an escape sequence for a terminal emulator.  NOTE: the vendor disputes the significance of this report, stating that &amp;#34;This is not a security problem in Varnish or any other piece of software which writes a logfile. The real problem is the mistaken belief that you can cat(1) a random logfile to your terminal safely.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Varnish 2.0.6 writes data to a log file without sanitizing non-printable characters, which might allow remote attackers to modify a window&amp;#39;s title, or possibly execute arbitrary commands or overwrite files, via an HTTP request containing an escape sequence for a terminal emulator.  NOTE: the vendor disputes the significance of this report, stating that &amp;#34;This is not a security problem in Varnish or any other piece of software which writes a logfile. The real problem is the mistaken belief that you can cat(1) a random logfile to your terminal safely.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2009-4488</guid>
    </item>
    <item>
      <title>GHSA-xm68-4v8h-h9rf</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-xm68-4v8h-h9rf</link>
      <description>&lt;p&gt;** DISPUTED ** Varnish 2.0.6 writes data to a log file without sanitizing non-printable characters, which might allow remote attackers to modify a window&amp;#39;s title, or possibly execute arbitrary commands or overwrite files, via an HTTP request containing an escape sequence for a terminal emulator.  NOTE: the vendor disputes the significance of this report, stating that &amp;#34;This is not a security problem in Varnish or any other piece of software which writes a logfile. The real problem is the mistaken belief that you can cat(1) a random logfile to your terminal safely.&amp;#34;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;** DISPUTED ** Varnish 2.0.6 writes data to a log file without sanitizing non-printable characters, which might allow remote attackers to modify a window&amp;#39;s title, or possibly execute arbitrary commands or overwrite files, via an HTTP request containing an escape sequence for a terminal emulator.  NOTE: the vendor disputes the significance of this report, stating that &amp;#34;This is not a security problem in Varnish or any other piece of software which writes a logfile. The real problem is the mistaken belief that you can cat(1) a random logfile to your terminal safely.&amp;#34;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-xm68-4v8h-h9rf</guid>
    </item>
    <item>
      <title>gsd-2009-4488</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2009-4488</link>
      <description>gsd-2009-4488</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2009-4488</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2009-4488</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2009-4488</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:14.04:LTS: varnish, Ubuntu:Pro:16.04:LTS: varnish&lt;/p&gt;
&lt;p&gt;Varnish 2.0.6 writes data to a log file without sanitizing non-printable characters, which might allow remote attackers to modify a window&amp;#39;s title, or possibly execute arbitrary commands or overwrite files, via an HTTP request containing an escape sequence for a terminal emulator.  NOTE: the vendor disputes the significance of this report, stating that &amp;#34;This is not a security problem in Varnish or any other piece of software which writes a logfile. The real problem is the mistaken belief that you can cat(1) a random logfile to your terminal safely.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:14.04:LTS: varnish, Ubuntu:Pro:16.04:LTS: varnish&lt;/p&gt;
&lt;p&gt;Varnish 2.0.6 writes data to a log file without sanitizing non-printable characters, which might allow remote attackers to modify a window&amp;#39;s title, or possibly execute arbitrary commands or overwrite files, via an HTTP request containing an escape sequence for a terminal emulator.  NOTE: the vendor disputes the significance of this report, stating that &amp;#34;This is not a security problem in Varnish or any other piece of software which writes a logfile. The real problem is the mistaken belief that you can cat(1) a random logfile to your terminal safely.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2009-4488</guid>
    </item>
  </channel>
</rss>
