<?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:36 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-389277</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-389277</link>
      <description>EUVD-2026-389277</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-389277</guid>
    </item>
    <item>
      <title>fkie_cve-2026-85250</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-85250</link>
      <description>&lt;p&gt;Improper Restriction of XML External Entity Reference vulnerability in Apache Camel XPath component.&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;With documentType set to InputSource, XPathBuilder handed the payload straight to javax.xml.xpath, which builds a DocumentBuilder of its own using the JDK defaults. The hardening applied to Camel&amp;#39;s default document type was therefore bypassed: a DOCTYPE declaration that is refused on the default type was accepted here, and the external entity it declared was resolved and expanded into the evaluated document. An external sender whose XML reaches such an expression could read files readable by the Camel process and cause the process to issue requests to hosts it names. The two document types disagreeing on parser configuration is what made this reachable, since a deployment choosing InputSource for streaming reasons had no indication it was also choosing a weaker parser.&lt;/p&gt;
&lt;p&gt;Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. The InputSource document type now goes through the same hardened parser as the default type, so a DOCTYPE is refused. Note that it also shares that type&amp;#39;s documented escape hatch: the same DocumentBuilderFactory system properties that relax the default type relax this one, so a deployment that has set them remains unprotected by design. For…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Improper Restriction of XML External Entity Reference vulnerability in Apache Camel XPath component.&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;With documentType set to InputSource, XPathBuilder handed the payload straight to javax.xml.xpath, which builds a DocumentBuilder of its own using the JDK defaults. The hardening applied to Camel&amp;#39;s default document type was therefore bypassed: a DOCTYPE declaration that is refused on the default type was accepted here, and the external entity it declared was resolved and expanded into the evaluated document. An external sender whose XML reaches such an expression could read files readable by the Camel process and cause the process to issue requests to hosts it names. The two document types disagreeing on parser configuration is what made this reachable, since a deployment choosing InputSource for streaming reasons had no indication it was also choosing a weaker parser.&lt;/p&gt;
&lt;p&gt;Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. The InputSource document type now goes through the same hardened parser as the default type, so a DOCTYPE is refused. Note that it also shares that type&amp;#39;s documented escape hatch: the same DocumentBuilderFactory system properties that relax the default type relax this one, so a deployment that has set them remains unprotected by design. For…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-85250</guid>
    </item>
    <item>
      <title>GHSA-x9f8-58m2-93q2</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-x9f8-58m2-93q2</link>
      <description>&lt;p&gt;Improper Restriction of XML External Entity Reference vulnerability in Apache Camel XPath component.&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;With documentType set to InputSource, XPathBuilder handed the payload straight to javax.xml.xpath, which builds a DocumentBuilder of its own using the JDK defaults. The hardening applied to Camel&amp;#39;s default document type was therefore bypassed: a DOCTYPE declaration that is refused on the default type was accepted here, and the external entity it declared was resolved and expanded into the evaluated document. An external sender whose XML reaches such an expression could read files readable by the Camel process and cause the process to issue requests to hosts it names. The two document types disagreeing on parser configuration is what made this reachable, since a deployment choosing InputSource for streaming reasons had no indication it was also choosing a weaker parser.&lt;/p&gt;
&lt;p&gt;Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. The InputSource document type now goes through the same hardened parser as the default type, so a DOCTYPE is refused. Note that it also shares that type&amp;#39;s documented escape hatch: the same DocumentBuilderFactory system properties that relax the default type relax this one, so a deployment that has set them remains unprotected by design. For…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Improper Restriction of XML External Entity Reference vulnerability in Apache Camel XPath component.&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;With documentType set to InputSource, XPathBuilder handed the payload straight to javax.xml.xpath, which builds a DocumentBuilder of its own using the JDK defaults. The hardening applied to Camel&amp;#39;s default document type was therefore bypassed: a DOCTYPE declaration that is refused on the default type was accepted here, and the external entity it declared was resolved and expanded into the evaluated document. An external sender whose XML reaches such an expression could read files readable by the Camel process and cause the process to issue requests to hosts it names. The two document types disagreeing on parser configuration is what made this reachable, since a deployment choosing InputSource for streaming reasons had no indication it was also choosing a weaker parser.&lt;/p&gt;
&lt;p&gt;Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. The InputSource document type now goes through the same hardened parser as the default type, so a DOCTYPE is refused. Note that it also shares that type&amp;#39;s documented escape hatch: the same DocumentBuilderFactory system properties that relax the default type relax this one, so a deployment that has set them remains unprotected by design. For…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-x9f8-58m2-93q2</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>
