<?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, 20 Nov 2026 19:40:24 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-394907</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-394907</link>
      <description>EUVD-2026-394907</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-394907</guid>
    </item>
    <item>
      <title>fkie_cve-2026-92709</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-92709</link>
      <description>&lt;p&gt;Rsyslog is a rocket-fast system for log processing. From versions 1.15.0 to 8.2610.0, rsyslog&amp;#39;s omfile dynaFile facility intentionally allows templates to generate flexible output paths. This supports valid deployments that route logs into different directories or use dynamically generated file names. A deployment becomes unsafe when a dynaFile template uses a value influenced by untrusted input as a path component without explicit secure-path handling. In that configuration, the rendered path can escape the operator&amp;#39;s intended log directory. This is not limited to the RFC5424 HOSTNAME field. Any untrusted value that reaches a dynaFile path component can create the condition. At time of publication, there are no publicly available patches.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Rsyslog is a rocket-fast system for log processing. From versions 1.15.0 to 8.2610.0, rsyslog&amp;#39;s omfile dynaFile facility intentionally allows templates to generate flexible output paths. This supports valid deployments that route logs into different directories or use dynamically generated file names. A deployment becomes unsafe when a dynaFile template uses a value influenced by untrusted input as a path component without explicit secure-path handling. In that configuration, the rendered path can escape the operator&amp;#39;s intended log directory. This is not limited to the RFC5424 HOSTNAME field. Any untrusted value that reaches a dynaFile path component can create the condition. At time of publication, there are no publicly available patches.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-92709</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-92709 — Rsyslog: DynFile Path Traversal → Arbitrary File Write as Root → RCE</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-92709</link>
      <description>msrc_CVE-2026-92709</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-92709</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-92709</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-92709</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:14.04:LTS: rsyslog, Ubuntu:Pro:16.04:LTS: rsyslog, Ubuntu:Pro:18.04:LTS: rsyslog, Ubuntu:Pro:20.04:LTS: rsyslog, Ubuntu:22.04:LTS: rsyslog, Ubuntu:24.04:LTS: rsyslog, Ubuntu:26.10: rsyslog, Ubuntu:26.04:LTS: rsyslog&lt;/p&gt;
&lt;p&gt;Rsyslog is a rocket-fast system for log processing. From versions 1.15.0 to 8.2610.0, rsyslog&amp;#39;s omfile dynaFile facility intentionally allows templates to generate flexible output paths. This supports valid deployments that route logs into different directories or use dynamically generated file names. A deployment becomes unsafe when a dynaFile template uses a value influenced by untrusted input as a path component without explicit secure-path handling. In that configuration, the rendered path can escape the operator&amp;#39;s intended log directory. This is not limited to the RFC5424 HOSTNAME field. Any untrusted value that reaches a dynaFile path component can create the condition. At time of publication, there are no publicly available patches.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:14.04:LTS: rsyslog, Ubuntu:Pro:16.04:LTS: rsyslog, Ubuntu:Pro:18.04:LTS: rsyslog, Ubuntu:Pro:20.04:LTS: rsyslog, Ubuntu:22.04:LTS: rsyslog, Ubuntu:24.04:LTS: rsyslog, Ubuntu:26.10: rsyslog, Ubuntu:26.04:LTS: rsyslog&lt;/p&gt;
&lt;p&gt;Rsyslog is a rocket-fast system for log processing. From versions 1.15.0 to 8.2610.0, rsyslog&amp;#39;s omfile dynaFile facility intentionally allows templates to generate flexible output paths. This supports valid deployments that route logs into different directories or use dynamically generated file names. A deployment becomes unsafe when a dynaFile template uses a value influenced by untrusted input as a path component without explicit secure-path handling. In that configuration, the rendered path can escape the operator&amp;#39;s intended log directory. This is not limited to the RFC5424 HOSTNAME field. Any untrusted value that reaches a dynaFile path component can create the condition. At time of publication, there are no publicly available patches.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-92709</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4119 — rsyslog: Schwachstelle ermöglicht Manipulation von Dateien</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4119</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in rsyslog ausnutzen, um Dateien zu manipulieren.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in rsyslog ausnutzen, um Dateien zu manipulieren.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4119</guid>
    </item>
  </channel>
</rss>
