<?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>Sat, 03 Oct 2026 11:12:32 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-09302</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-09302</link>
      <description>bdu:2026-09302</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-09302</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0877 — De multiples vulnérabilités ont été découvertes dans les produits SAP. Certaines d'entre elles permettent à un attaquan…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0877</link>
      <description>certfr-2026-avi-0877</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0877</guid>
    </item>
    <item>
      <title>EUVD-2026-337336</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-337336</link>
      <description>EUVD-2026-337336</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-337336</guid>
    </item>
    <item>
      <title>fkie_cve-2026-33454</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-33454</link>
      <description>&lt;p&gt;The Camel-Mail component is vulnerable to Camel message header injection. The custom header filter strategy used by the component (MailHeaderFilterStrategy) only filters the &amp;#39;out&amp;#39; direction via setOutFilterStartsWith, while it does not configure the &amp;#39;in&amp;#39; direction via setInFilterStartsWith. As a result, when a Camel application consumes mail through camel-mail (for example via from(\&amp;#34;imap://...\&amp;#34;) or from(\&amp;#34;pop3://...\&amp;#34;)) the inbound filter check is skipped and Camel-prefixed MIME headers are mapped unfiltered into the Exchange. An attacker who can deliver an email to a mailbox monitored by such a consumer can inject Camel-specific headers that, for some Camel components downstream of the mail consumer (such as camel-bean, camel-exec, or camel-sql), can alter the behaviour of the route. This is the same pattern that was previously addressed in camel-undertow (CVE-2025-30177) and the broader incoming-header filter (CVE-2025-27636 and CVE-2025-29891).&lt;/p&gt;
&lt;p&gt;This issue affects Apache Camel: from 3.0.0 before 4.14.6, from 4.15.0 before 4.18.1.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to version 4.19.0, which fixes the issue. If users are on the 4.18.x LTS releases stream, then they are suggested to upgrade to 4.18.1. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.6.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Camel-Mail component is vulnerable to Camel message header injection. The custom header filter strategy used by the component (MailHeaderFilterStrategy) only filters the &amp;#39;out&amp;#39; direction via setOutFilterStartsWith, while it does not configure the &amp;#39;in&amp;#39; direction via setInFilterStartsWith. As a result, when a Camel application consumes mail through camel-mail (for example via from(\&amp;#34;imap://...\&amp;#34;) or from(\&amp;#34;pop3://...\&amp;#34;)) the inbound filter check is skipped and Camel-prefixed MIME headers are mapped unfiltered into the Exchange. An attacker who can deliver an email to a mailbox monitored by such a consumer can inject Camel-specific headers that, for some Camel components downstream of the mail consumer (such as camel-bean, camel-exec, or camel-sql), can alter the behaviour of the route. This is the same pattern that was previously addressed in camel-undertow (CVE-2025-30177) and the broader incoming-header filter (CVE-2025-27636 and CVE-2025-29891).&lt;/p&gt;
&lt;p&gt;This issue affects Apache Camel: from 3.0.0 before 4.14.6, from 4.15.0 before 4.18.1.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to version 4.19.0, which fixes the issue. If users are on the 4.18.x LTS releases stream, then they are suggested to upgrade to 4.18.1. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.6.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-33454</guid>
    </item>
    <item>
      <title>GHSA-2vqf-x7g4-7c2g — Apache Camel's Camel-Mail component is vulnerable to Camel message header injection</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2vqf-x7g4-7c2g</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.apache.camel:camel-mail&lt;/p&gt;
&lt;p&gt;The Camel-Mail component is vulnerable to Camel message header injection. The custom header filter strategy used by the component (MailHeaderFilterStrategy) only filters the &amp;#39;out&amp;#39; direction via setOutFilterStartsWith, while it does not configure the &amp;#39;in&amp;#39; direction via setInFilterStartsWith. As a result, when a Camel application consumes mail through camel-mail (for example via from(\&amp;#34;imap://...\&amp;#34;) or from(\&amp;#34;pop3://...\&amp;#34;)) the inbound filter check is skipped and Camel-prefixed MIME headers are mapped unfiltered into the Exchange. An attacker who can deliver an email to a mailbox monitored by such a consumer can inject Camel-specific headers that, for some Camel components downstream of the mail consumer (such as camel-bean, camel-exec, or camel-sql), can alter the behaviour of the route. This is the same pattern that was previously addressed in camel-undertow (CVE-2025-30177) and the broader incoming-header filter (CVE-2025-27636 and CVE-2025-29891).&lt;/p&gt;
&lt;p&gt;This issue affects Apache Camel: from 3.0.0 before 4.14.6, from 4.15.0 before 4.18.1.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to version 4.19.0, which fixes the issue. If users are on the 4.18.x LTS releases stream, then they are suggested to upgrade to 4.18.1. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.6.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.apache.camel:camel-mail&lt;/p&gt;
&lt;p&gt;The Camel-Mail component is vulnerable to Camel message header injection. The custom header filter strategy used by the component (MailHeaderFilterStrategy) only filters the &amp;#39;out&amp;#39; direction via setOutFilterStartsWith, while it does not configure the &amp;#39;in&amp;#39; direction via setInFilterStartsWith. As a result, when a Camel application consumes mail through camel-mail (for example via from(\&amp;#34;imap://...\&amp;#34;) or from(\&amp;#34;pop3://...\&amp;#34;)) the inbound filter check is skipped and Camel-prefixed MIME headers are mapped unfiltered into the Exchange. An attacker who can deliver an email to a mailbox monitored by such a consumer can inject Camel-specific headers that, for some Camel components downstream of the mail consumer (such as camel-bean, camel-exec, or camel-sql), can alter the behaviour of the route. This is the same pattern that was previously addressed in camel-undertow (CVE-2025-30177) and the broader incoming-header filter (CVE-2025-27636 and CVE-2025-29891).&lt;/p&gt;
&lt;p&gt;This issue affects Apache Camel: from 3.0.0 before 4.14.6, from 4.15.0 before 4.18.1.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to version 4.19.0, which fixes the issue. If users are on the 4.18.x LTS releases stream, then they are suggested to upgrade to 4.18.1. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.6.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2vqf-x7g4-7c2g</guid>
    </item>
    <item>
      <title>NCSC-2026-0129 — Kwetsbaarheden verholpen in Apache Camel</title>
      <link>https://cve.radiocsirt.org/vuln/ncsc-2026-0129</link>
      <description>NCSC-2026-0129</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ncsc-2026-0129</guid>
    </item>
    <item>
      <title>RHSA-2026:17668 — Red Hat Security Advisory: Red Hat Build of Apache Camel 4.18.1 for Spring Boot release.</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:17668</link>
      <description>&lt;p&gt;bouncycastle: BC-JAVA: GOSTCTR implementation unable to process more than 255 blocks correctly org.codehaus.plexus:plexus-utils: Plexus-utils: Directory Traversal in extractFile method bouncycastle: BC-JAVA: LDAP injection vulnerability in LDAPStoreHelper.java org.eclipse.jetty/jetty-http: HTTP request smuggling via chunked extension quoted-string parsing bouncycastle: BC-JAVA: unbounded PGP AEAD chunk size leads to pre-auth resource exhaustion bouncycastle: BC-JAVA: PKIX draft CompositeVerifier accepts empty signature sequence as valid org.eclipse.jetty.ee10/jetty-ee10: early return from the JASPIAuthenticator class without clearing ThreadLocal variables camel-infinispan: camel-infinispan: Remote Code Execution via Unsafe Deserialization Spring Boot: Spring Boot: Authentication bypass via misconfigured Health Group additional path org.apache.artemis:artemis-server: org.apache.activemq:artemis-server: Apache Artemis, Apache ActiveMQ Artemis: Message injection and exfiltration due to missing authentication Apache Camel: camel-coap: Apache Camel camel-coap: Remote code execution via CoAP URI query parameter injection Apache Camel: Camel-Mail: Camel-Mail: Altered application behavior via header injection io.netty/netty-codec-http: Netty: Request smuggling via incorrect parsing of HTTP/1.1 chunked transfer encoding extension values netty: Netty: Denial of Service via HTTP/2 CONTINUATION frame flood Apache Kafka Clients: Apache Kafka Clients: Information disclosure and data corru…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;bouncycastle: BC-JAVA: GOSTCTR implementation unable to process more than 255 blocks correctly org.codehaus.plexus:plexus-utils: Plexus-utils: Directory Traversal in extractFile method bouncycastle: BC-JAVA: LDAP injection vulnerability in LDAPStoreHelper.java org.eclipse.jetty/jetty-http: HTTP request smuggling via chunked extension quoted-string parsing bouncycastle: BC-JAVA: unbounded PGP AEAD chunk size leads to pre-auth resource exhaustion bouncycastle: BC-JAVA: PKIX draft CompositeVerifier accepts empty signature sequence as valid org.eclipse.jetty.ee10/jetty-ee10: early return from the JASPIAuthenticator class without clearing ThreadLocal variables camel-infinispan: camel-infinispan: Remote Code Execution via Unsafe Deserialization Spring Boot: Spring Boot: Authentication bypass via misconfigured Health Group additional path org.apache.artemis:artemis-server: org.apache.activemq:artemis-server: Apache Artemis, Apache ActiveMQ Artemis: Message injection and exfiltration due to missing authentication Apache Camel: camel-coap: Apache Camel camel-coap: Remote code execution via CoAP URI query parameter injection Apache Camel: Camel-Mail: Camel-Mail: Altered application behavior via header injection io.netty/netty-codec-http: Netty: Request smuggling via incorrect parsing of HTTP/1.1 chunked transfer encoding extension values netty: Netty: Denial of Service via HTTP/2 CONTINUATION frame flood Apache Kafka Clients: Apache Kafka Clients: Information disclosure and data corru…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:17668</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1271 — Apache Camel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1271</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Apache Camel ausnutzen, um beliebigen Programmcode auszuführen, Daten zu manipulieren oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Apache Camel ausnutzen, um beliebigen Programmcode auszuführen, Daten zu manipulieren oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1271</guid>
    </item>
  </channel>
</rss>
