<?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>Sun, 04 Oct 2026 01:06:50 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-05260</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-05260</link>
      <description>bdu:2026-05260</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-05260</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0627 — De multiples vulnérabilités ont été découvertes dans les produits Splunk. Certaines d'entre elles permettent à un attaq…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0627</link>
      <description>certfr-2026-avi-0627</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0627</guid>
    </item>
    <item>
      <title>Withdrawn: CLEANSTART-2026-AA33839 — Security fixes in activemq 6.2.3-r1</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-aa33839</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: activemq&lt;/p&gt;
&lt;p&gt;Package activemq version 6.2.3-r1 fixes 10 vulnerabilities: CVE-2026-34477, CVE-2026-34478, CVE-2026-34480, CVE-2026-22745, CVE-2026-22741...&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: activemq&lt;/p&gt;
&lt;p&gt;Package activemq version 6.2.3-r1 fixes 10 vulnerabilities: CVE-2026-34477, CVE-2026-34478, CVE-2026-34480, CVE-2026-22745, CVE-2026-22741...&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-aa33839</guid>
    </item>
    <item>
      <title>EUVD-2026-290461</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-290461</link>
      <description>EUVD-2026-290461</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-290461</guid>
    </item>
    <item>
      <title>fkie_cve-2026-34478</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-34478</link>
      <description>&lt;p&gt;Apache Log4j Core&amp;#39;s  Rfc5424Layout https://logging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout , in versions 2.21.0 through 2.25.3, is vulnerable to log injection via CRLF sequences due to undocumented renames of security-relevant configuration attributes.&lt;/p&gt;
&lt;p&gt;Two distinct issues affect users of stream-based syslog services who configure Rfc5424Layout directly:&lt;/p&gt;
&lt;p&gt;*  The newLineEscape attribute was silently renamed, causing newline escaping to stop working for users of TCP framing (RFC 6587), exposing them to CRLF injection in log output.
  *  The useTlsMessageFormat attribute was silently renamed, causing users of TLS framing (RFC 5425) to be silently downgraded to unframed TCP (RFC 6587), without newline escaping.&lt;/p&gt;
&lt;p&gt;Users of the SyslogAppender are not affected, as its configuration attributes were not modified.&lt;/p&gt;
&lt;p&gt;Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Apache Log4j Core&amp;#39;s  Rfc5424Layout https://logging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout , in versions 2.21.0 through 2.25.3, is vulnerable to log injection via CRLF sequences due to undocumented renames of security-relevant configuration attributes.&lt;/p&gt;
&lt;p&gt;Two distinct issues affect users of stream-based syslog services who configure Rfc5424Layout directly:&lt;/p&gt;
&lt;p&gt;*  The newLineEscape attribute was silently renamed, causing newline escaping to stop working for users of TCP framing (RFC 6587), exposing them to CRLF injection in log output.
  *  The useTlsMessageFormat attribute was silently renamed, causing users of TLS framing (RFC 5425) to be silently downgraded to unframed TCP (RFC 6587), without newline escaping.&lt;/p&gt;
&lt;p&gt;Users of the SyslogAppender are not affected, as its configuration attributes were not modified.&lt;/p&gt;
&lt;p&gt;Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-34478</guid>
    </item>
    <item>
      <title>GHSA-445c-vh5m-36rj — Apache Log4j Core: log injection in `Rfc5424Layout` due to silent configuration incompatibility</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-445c-vh5m-36rj</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.apache.logging.log4j:log4j-core&lt;/p&gt;
&lt;p&gt;Apache Log4j Core&amp;#39;s [`Rfc5424Layout`](https://logging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout), in versions 2.21.0 through 2.25.3, is vulnerable to log injection via CRLF sequences due to undocumented renames of security-relevant configuration attributes.&lt;/p&gt;
&lt;p&gt;Two distinct issues affect users of stream-based syslog services who configure Rfc5424Layout directly:&lt;/p&gt;
&lt;p&gt;*  The `newLineEscape` attribute was silently renamed, causing newline escaping to stop working for users of TCP framing (RFC 6587), exposing them to CRLF injection in log output.
  *  The `useTlsMessageFormat` attribute was silently renamed, causing users of TLS framing (RFC 5425) to be silently downgraded to unframed TCP (RFC 6587), without newline escaping.&lt;/p&gt;
&lt;p&gt;Users of the `SyslogAppender` are not affected, as its configuration attributes were not modified.&lt;/p&gt;
&lt;p&gt;Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.apache.logging.log4j:log4j-core&lt;/p&gt;
&lt;p&gt;Apache Log4j Core&amp;#39;s [`Rfc5424Layout`](https://logging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout), in versions 2.21.0 through 2.25.3, is vulnerable to log injection via CRLF sequences due to undocumented renames of security-relevant configuration attributes.&lt;/p&gt;
&lt;p&gt;Two distinct issues affect users of stream-based syslog services who configure Rfc5424Layout directly:&lt;/p&gt;
&lt;p&gt;*  The `newLineEscape` attribute was silently renamed, causing newline escaping to stop working for users of TCP framing (RFC 6587), exposing them to CRLF injection in log output.
  *  The `useTlsMessageFormat` attribute was silently renamed, causing users of TLS framing (RFC 5425) to be silently downgraded to unframed TCP (RFC 6587), without newline escaping.&lt;/p&gt;
&lt;p&gt;Users of the `SyslogAppender` are not affected, as its configuration attributes were not modified.&lt;/p&gt;
&lt;p&gt;Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-445c-vh5m-36rj</guid>
    </item>
    <item>
      <title>RHSA-2026:21773 — Red Hat Security Advisory: Red Hat Offline Knowledge Portal security and content update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:21773</link>
      <description>&lt;p&gt;org.eclipse.jetty/jetty-http: org.eclipse.jetty: Security bypass due to differential URI parsing org.eclipse.jetty/jetty-http: HTTP request smuggling via chunked extension quoted-string parsing org.apache.logging.log4j/log4j-core: Apache Log4j Core: Man-in-the-middle attack due to incomplete hostname verification org.apache.logging.log4j/log4j-core: Apache Log4j Core: Log injection via CRLF sequences due to configuration attribute renames org.apache.logging.log4j/log4j-1.2-api: Apache Log4j 1-to-Log4j 2 bridge: Log processing denial of service due to improper XML escaping org.apache.logging.log4j/log4j-core: Apache Log4j Core: Invalid XML output causes denial of service in logging org.apache.logging.log4j: Apache Log4j JsonTemplateLayout: Denial of Service via invalid JSON output&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;org.eclipse.jetty/jetty-http: org.eclipse.jetty: Security bypass due to differential URI parsing org.eclipse.jetty/jetty-http: HTTP request smuggling via chunked extension quoted-string parsing org.apache.logging.log4j/log4j-core: Apache Log4j Core: Man-in-the-middle attack due to incomplete hostname verification org.apache.logging.log4j/log4j-core: Apache Log4j Core: Log injection via CRLF sequences due to configuration attribute renames org.apache.logging.log4j/log4j-1.2-api: Apache Log4j 1-to-Log4j 2 bridge: Log processing denial of service due to improper XML escaping org.apache.logging.log4j/log4j-core: Apache Log4j Core: Invalid XML output causes denial of service in logging org.apache.logging.log4j: Apache Log4j JsonTemplateLayout: Denial of Service via invalid JSON output&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:21773</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-34478</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-34478</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: apache-log4j1.2, Ubuntu:Pro:16.04:LTS: apache-log4j2, Ubuntu:Pro:16.04:LTS: apache-log4j1.2, Ubuntu:18.04:LTS: apache-log4j1.2, Ubuntu:18.04:LTS: apache-log4j2, Ubuntu:20.04:LTS: apache-log4j1.2, Ubuntu:20.04:LTS: apache-log4j2, Ubuntu:22.04:LTS: apache-log4j1.2, Ubuntu:22.04:LTS: apache-log4j2, Ubuntu:24.04:LTS: apache-log4j1.2 and 5 more&lt;/p&gt;
&lt;p&gt;Apache Log4j Core&amp;#39;s  Rfc5424Layout https://logging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout , in versions 2.21.0 through 2.25.3, is vulnerable to log injection via CRLF sequences due to undocumented renames of security-relevant configuration attributes. Two distinct issues affect users of stream-based syslog services who configure Rfc5424Layout directly:   *  The newLineEscape attribute was silently renamed, causing newline escaping to stop working for users of TCP framing (RFC 6587), exposing them to CRLF injection in log output.   *  The useTlsMessageFormat attribute was silently renamed, causing users of TLS framing (RFC 5425) to be silently downgraded to unframed TCP (RFC 6587), without newline escaping. Users of the SyslogAppender are not affected, as its configuration attributes were not modified. Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: apache-log4j1.2, Ubuntu:Pro:16.04:LTS: apache-log4j2, Ubuntu:Pro:16.04:LTS: apache-log4j1.2, Ubuntu:18.04:LTS: apache-log4j1.2, Ubuntu:18.04:LTS: apache-log4j2, Ubuntu:20.04:LTS: apache-log4j1.2, Ubuntu:20.04:LTS: apache-log4j2, Ubuntu:22.04:LTS: apache-log4j1.2, Ubuntu:22.04:LTS: apache-log4j2, Ubuntu:24.04:LTS: apache-log4j1.2 and 5 more&lt;/p&gt;
&lt;p&gt;Apache Log4j Core&amp;#39;s  Rfc5424Layout https://logging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout , in versions 2.21.0 through 2.25.3, is vulnerable to log injection via CRLF sequences due to undocumented renames of security-relevant configuration attributes. Two distinct issues affect users of stream-based syslog services who configure Rfc5424Layout directly:   *  The newLineEscape attribute was silently renamed, causing newline escaping to stop working for users of TCP framing (RFC 6587), exposing them to CRLF injection in log output.   *  The useTlsMessageFormat attribute was silently renamed, causing users of TLS framing (RFC 5425) to be silently downgraded to unframed TCP (RFC 6587), without newline escaping. Users of the SyslogAppender are not affected, as its configuration attributes were not modified. Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-34478</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1067 — Apache log4j: Mehrere Schwachstellen ermöglichen Manipulation von Dateien</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1067</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Apache log4j ausnutzen, um Dateien zu manipulieren.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Apache log4j ausnutzen, um Dateien zu manipulieren.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1067</guid>
    </item>
  </channel>
</rss>
