<?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 17:51:59 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-395649</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-395649</link>
      <description>EUVD-2026-395649</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-395649</guid>
    </item>
    <item>
      <title>fkie_cve-2026-18894</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-18894</link>
      <description>&lt;p&gt;IBM Langflow OSS 1.0.0 through 1.12.4 could allow a remote attacker to trigger pre-existing stored Python component code in a public workflow, executing it under the flow owner&amp;#39;s runtime context within the server process. This bypasses the intended trust boundary where public execution paths are restricted to server-trusted component code.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;IBM Langflow OSS 1.0.0 through 1.12.4 could allow a remote attacker to trigger pre-existing stored Python component code in a public workflow, executing it under the flow owner&amp;#39;s runtime context within the server process. This bypasses the intended trust boundary where public execution paths are restricted to server-trusted component code.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-18894</guid>
    </item>
    <item>
      <title>GHSA-pf68-vvvh-6f8f</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-pf68-vvvh-6f8f</link>
      <description>&lt;p&gt;IBM Langflow OSS 1.0.0 through 1.12.4 could allow a remote attacker to trigger pre-existing stored Python component code in a public workflow, executing it under the flow owner&amp;#39;s runtime context within the server process. This bypasses the intended trust boundary where public execution paths are restricted to server-trusted component code.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;IBM Langflow OSS 1.0.0 through 1.12.4 could allow a remote attacker to trigger pre-existing stored Python component code in a public workflow, executing it under the flow owner&amp;#39;s runtime context within the server process. This bypasses the intended trust boundary where public execution paths are restricted to server-trusted component code.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-pf68-vvvh-6f8f</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4041 — Langflow: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4041</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Langflow ausnutzen, um beliebigen Programmcode auszuführen, um einen Denial of Service Angriff durchzufü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 Langflow ausnutzen, um beliebigen Programmcode auszuführen, um einen Denial of Service Angriff durchzufü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-4041</guid>
    </item>
  </channel>
</rss>
