<?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, 16 Nov 2026 19:57:48 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-389403</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-389403</link>
      <description>EUVD-2026-389403</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-389403</guid>
    </item>
    <item>
      <title>fkie_cve-2026-78164</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-78164</link>
      <description>&lt;p&gt;Improper Neutralization of Special Elements Used in a Template Engine and Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Camel HTTP, Netty HTTP, Undertow and Vert.x HTTP components.&lt;/p&gt;
&lt;p&gt;This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.&lt;/p&gt;
&lt;p&gt;The Camel HTTP producer families let an inbound message override the endpoint URI through the CamelHttpUri and CamelRestHttpUri headers, and then passed that message-supplied string through CamelContext.resolvePropertyPlaceholders() before using it. Property-placeholder resolution is a configuration-resolution facility, not a URI-parsing step: it reaches operating-system environment variables, JVM system properties, every PropertiesFunction registered on the classpath - including the secret functions - and, through camel-bean, the invocation of a no-argument method on any bean in the registry. Applying it to Exchange content therefore turned a URI string into a configuration- and bean-evaluation context. A route author opted into none of this: a plain static to(&amp;#34;http://backend/api&amp;#34;) was sufficient. Seven call sites were affected: HttpHelper.createURL and HttpHelper.createMethod in camel-http-common, HttpMethodHelper.createMethod in camel-http, VertxHttpHelper.resolveHttpURI in camel-vertx-http, UndertowHelper.createURL and UndertowHelper.createMethod in camel-undertow, and NettyHttpHelper.createURL in camel-netty-http. The bridgeEndpoint option did not bound the exposure…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Improper Neutralization of Special Elements Used in a Template Engine and Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Camel HTTP, Netty HTTP, Undertow and Vert.x HTTP components.&lt;/p&gt;
&lt;p&gt;This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.&lt;/p&gt;
&lt;p&gt;The Camel HTTP producer families let an inbound message override the endpoint URI through the CamelHttpUri and CamelRestHttpUri headers, and then passed that message-supplied string through CamelContext.resolvePropertyPlaceholders() before using it. Property-placeholder resolution is a configuration-resolution facility, not a URI-parsing step: it reaches operating-system environment variables, JVM system properties, every PropertiesFunction registered on the classpath - including the secret functions - and, through camel-bean, the invocation of a no-argument method on any bean in the registry. Applying it to Exchange content therefore turned a URI string into a configuration- and bean-evaluation context. A route author opted into none of this: a plain static to(&amp;#34;http://backend/api&amp;#34;) was sufficient. Seven call sites were affected: HttpHelper.createURL and HttpHelper.createMethod in camel-http-common, HttpMethodHelper.createMethod in camel-http, VertxHttpHelper.resolveHttpURI in camel-vertx-http, UndertowHelper.createURL and UndertowHelper.createMethod in camel-undertow, and NettyHttpHelper.createURL in camel-netty-http. The bridgeEndpoint option did not bound the exposure…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-78164</guid>
    </item>
    <item>
      <title>GHSA-394j-cc2x-w9wm</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-394j-cc2x-w9wm</link>
      <description>&lt;p&gt;Improper Neutralization of Special Elements Used in a Template Engine and Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Camel HTTP, Netty HTTP, Undertow and Vert.x HTTP components.&lt;/p&gt;
&lt;p&gt;This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.&lt;/p&gt;
&lt;p&gt;The Camel HTTP producer families let an inbound message override the endpoint URI through the CamelHttpUri and CamelRestHttpUri headers, and then passed that message-supplied string through CamelContext.resolvePropertyPlaceholders() before using it. Property-placeholder resolution is a configuration-resolution facility, not a URI-parsing step: it reaches operating-system environment variables, JVM system properties, every PropertiesFunction registered on the classpath - including the AWS, Azure, GCP, HashiCorp, IBM, CyberArk and Kubernetes secret functions - and, through camel-bean, the invocation of a no-argument method on any bean in the registry. Applying it to Exchange content therefore turned a URI string into a configuration- and bean-evaluation context. A route author opted into none of this: a plain static to(&amp;#34;http://backend/api&amp;#34;) was sufficient. Seven call sites were affected: HttpHelper.createURL and HttpHelper.createMethod in camel-http-common, HttpMethodHelper.createMethod in camel-http, VertxHttpHelper.resolveHttpURI in camel-vertx-http, UndertowHelper.createURL and UndertowHelper.createMethod in camel-undertow, and NettyHttpHelper.createURL in camel-netty-h…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Improper Neutralization of Special Elements Used in a Template Engine and Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Camel HTTP, Netty HTTP, Undertow and Vert.x HTTP components.&lt;/p&gt;
&lt;p&gt;This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.&lt;/p&gt;
&lt;p&gt;The Camel HTTP producer families let an inbound message override the endpoint URI through the CamelHttpUri and CamelRestHttpUri headers, and then passed that message-supplied string through CamelContext.resolvePropertyPlaceholders() before using it. Property-placeholder resolution is a configuration-resolution facility, not a URI-parsing step: it reaches operating-system environment variables, JVM system properties, every PropertiesFunction registered on the classpath - including the AWS, Azure, GCP, HashiCorp, IBM, CyberArk and Kubernetes secret functions - and, through camel-bean, the invocation of a no-argument method on any bean in the registry. Applying it to Exchange content therefore turned a URI string into a configuration- and bean-evaluation context. A route author opted into none of this: a plain static to(&amp;#34;http://backend/api&amp;#34;) was sufficient. Seven call sites were affected: HttpHelper.createURL and HttpHelper.createMethod in camel-http-common, HttpMethodHelper.createMethod in camel-http, VertxHttpHelper.resolveHttpURI in camel-vertx-http, UndertowHelper.createURL and UndertowHelper.createMethod in camel-undertow, and NettyHttpHelper.createURL in camel-netty-h…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-394j-cc2x-w9wm</guid>
    </item>
    <item>
      <title>RHSA-2026:98783 — Red Hat Security Advisory: Red Hat Build of Apache Camel 4.22 for Quarkus 3.40 update is now available (RHBQ 3.40.1.GA)</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:98783</link>
      <description>&lt;p&gt;org.apache.camel/camel-mail: Apache Camel: Injected MIME headers can manipulate route behavior org.apache.camel/camel-http-common: org.apache.camel/camel-http: org.apache.camel/camel-vertx-http: org.apache.camel/camel-undertow: org.apache.camel/camel-netty-http: Apache Camel: information disclosure via improper property placeholder evaluation in HTTP headers org.apache.camel/camel-ftp: camel-ftp: Unauthorized remote file access via path traversal org.apache.camel/camel-mina-sftp: Apache Camel Mina SFTP: Unauthorized file access via path traversal org.apache.camel/camel-smb: camel-smb: Unauthorized file access via path traversal org.apache.camel/camel-netty-http: Apache Camel Netty HTTP: Security constraint bypass via case sensitivity mismatch org.apache.camel/camel-xpath: camel-xpath: Information disclosure via XML external entity references org.apache.camel/camel-http: camel-http: Information disclosure via improper credential handling during HTTP redirects org.apache.camel/camel-smooks: camel-smooks: Information disclosure via XML external entity injection&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;org.apache.camel/camel-mail: Apache Camel: Injected MIME headers can manipulate route behavior org.apache.camel/camel-http-common: org.apache.camel/camel-http: org.apache.camel/camel-vertx-http: org.apache.camel/camel-undertow: org.apache.camel/camel-netty-http: Apache Camel: information disclosure via improper property placeholder evaluation in HTTP headers org.apache.camel/camel-ftp: camel-ftp: Unauthorized remote file access via path traversal org.apache.camel/camel-mina-sftp: Apache Camel Mina SFTP: Unauthorized file access via path traversal org.apache.camel/camel-smb: camel-smb: Unauthorized file access via path traversal org.apache.camel/camel-netty-http: Apache Camel Netty HTTP: Security constraint bypass via case sensitivity mismatch org.apache.camel/camel-xpath: camel-xpath: Information disclosure via XML external entity references org.apache.camel/camel-http: camel-http: Information disclosure via improper credential handling during HTTP redirects org.apache.camel/camel-smooks: camel-smooks: Information disclosure via XML external entity injection&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:98783</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4006 — Apache Camel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4006</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Apache Camel ausnutzen, um beliebigen Programmcode auszuführen, um Informationen offenzulegen, um Dateien zu manipulieren und um Sicherheitsvorkehrungen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Apache Camel ausnutzen, um beliebigen Programmcode auszuführen, um Informationen offenzulegen, um Dateien zu manipulieren und um Sicherheitsvorkehrungen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4006</guid>
    </item>
  </channel>
</rss>
