<?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>Tue, 06 Oct 2026 11:52:27 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-02678</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-02678</link>
      <description>bdu:2024-02678</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-02678</guid>
    </item>
    <item>
      <title>cnvd-2024-26183</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2024-26183</link>
      <description>cnvd-2024-26183</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2024-26183</guid>
    </item>
    <item>
      <title>EUVD-2026-217351</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-217351</link>
      <description>EUVD-2026-217351</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-217351</guid>
    </item>
    <item>
      <title>fkie_cve-2024-27894</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-27894</link>
      <description>&lt;p&gt;The Pulsar Functions Worker includes a capability that permits authenticated users to create functions where the function&amp;#39;s implementation is referenced by a URL. The supported URL schemes include &amp;#34;file&amp;#34;, &amp;#34;http&amp;#34;, and &amp;#34;https&amp;#34;. When a function is created using this method, the Functions Worker will retrieve the implementation from the URL provided by the user. However, this feature introduces a vulnerability that can be exploited by an attacker to gain unauthorized access to any file that the Pulsar Functions Worker process has permissions to read. This includes reading the process environment which potentially includes sensitive information, such as secrets. Furthermore, an attacker could leverage this vulnerability to use the Pulsar Functions Worker as a proxy to access the content of remote HTTP and HTTPS endpoint URLs. This could also be used to carry out denial of service attacks.
This vulnerability also applies to the Pulsar Broker when it is configured with &amp;#34;functionsWorkerEnabled=true&amp;#34;.&lt;/p&gt;
&lt;p&gt;This issue affects Apache Pulsar versions from 2.4.0 to 2.10.5, from 2.11.0 to 2.11.3, from 3.0.0 to 3.0.2, from 3.1.0 to 3.1.2, and 3.2.0.&lt;/p&gt;
&lt;p&gt;2.10 Pulsar Function Worker users should upgrade to at least 2.10.6.
2.11 Pulsar Function Worker users should upgrade to at least 2.11.4.
3.0 Pulsar Function Worker users should upgrade to at least 3.0.3.
3.1 Pulsar Function Worker users should upgrade to at least 3.1.3.
3.2 Pulsar Function Worker users should upgrade to at least 3.2.1.&lt;/p&gt;
&lt;p&gt;Users op…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Pulsar Functions Worker includes a capability that permits authenticated users to create functions where the function&amp;#39;s implementation is referenced by a URL. The supported URL schemes include &amp;#34;file&amp;#34;, &amp;#34;http&amp;#34;, and &amp;#34;https&amp;#34;. When a function is created using this method, the Functions Worker will retrieve the implementation from the URL provided by the user. However, this feature introduces a vulnerability that can be exploited by an attacker to gain unauthorized access to any file that the Pulsar Functions Worker process has permissions to read. This includes reading the process environment which potentially includes sensitive information, such as secrets. Furthermore, an attacker could leverage this vulnerability to use the Pulsar Functions Worker as a proxy to access the content of remote HTTP and HTTPS endpoint URLs. This could also be used to carry out denial of service attacks.
This vulnerability also applies to the Pulsar Broker when it is configured with &amp;#34;functionsWorkerEnabled=true&amp;#34;.&lt;/p&gt;
&lt;p&gt;This issue affects Apache Pulsar versions from 2.4.0 to 2.10.5, from 2.11.0 to 2.11.3, from 3.0.0 to 3.0.2, from 3.1.0 to 3.1.2, and 3.2.0.&lt;/p&gt;
&lt;p&gt;2.10 Pulsar Function Worker users should upgrade to at least 2.10.6.
2.11 Pulsar Function Worker users should upgrade to at least 2.11.4.
3.0 Pulsar Function Worker users should upgrade to at least 3.0.3.
3.1 Pulsar Function Worker users should upgrade to at least 3.1.3.
3.2 Pulsar Function Worker users should upgrade to at least 3.2.1.&lt;/p&gt;
&lt;p&gt;Users op…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-27894</guid>
    </item>
    <item>
      <title>GHSA-c2x9-vw5h-39vc — Apache Pulsar: Pulsar Functions Worker Allows Unauthorized File Access and Unauthorized HTTP/HTTPS Proxying</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-c2x9-vw5h-39vc</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.apache.pulsar:pulsar-functions-worker&lt;/p&gt;
&lt;p&gt;The Pulsar Functions Worker includes a capability that permits authenticated users to create functions where the function&amp;#39;s implementation is referenced by a URL. The supported URL schemes include &amp;#34;file&amp;#34;, &amp;#34;http&amp;#34;, and &amp;#34;https&amp;#34;. When a function is created using this method, the Functions Worker will retrieve the implementation from the URL provided by the user. However, this feature introduces a vulnerability that can be exploited by an attacker to gain unauthorized access to any file that the Pulsar Functions Worker process has permissions to read. This includes reading the process environment which potentially includes sensitive information, such as secrets. Furthermore, an attacker could leverage this vulnerability to use the Pulsar Functions Worker as a proxy to access the content of remote HTTP and HTTPS endpoint URLs. This could also be used to carry out denial of service attacks.
This vulnerability also applies to the Pulsar Broker when it is configured with &amp;#34;functionsWorkerEnabled=true&amp;#34;.&lt;/p&gt;
&lt;p&gt;This issue affects Apache Pulsar versions from 2.4.0 to 2.10.5, from 2.11.0 to 2.11.3, from 3.0.0 to 3.0.2, from 3.1.0 to 3.1.2, and 3.2.0.&lt;/p&gt;
&lt;p&gt;2.10 Pulsar Function Worker users should upgrade to at least 2.10.6.
2.11 Pulsar Function Worker users should upgrade to at least 2.11.4.
3.0 Pulsar Function Worker users should upgrade to at least 3.0.3.
3.1 Pulsar Function Worker users should upgrade to at least 3.1.3.
3.2 Pulsar Function Worker users should upgrade to at least 3.2.1.&lt;/p&gt;
&lt;p&gt;Users op…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.apache.pulsar:pulsar-functions-worker&lt;/p&gt;
&lt;p&gt;The Pulsar Functions Worker includes a capability that permits authenticated users to create functions where the function&amp;#39;s implementation is referenced by a URL. The supported URL schemes include &amp;#34;file&amp;#34;, &amp;#34;http&amp;#34;, and &amp;#34;https&amp;#34;. When a function is created using this method, the Functions Worker will retrieve the implementation from the URL provided by the user. However, this feature introduces a vulnerability that can be exploited by an attacker to gain unauthorized access to any file that the Pulsar Functions Worker process has permissions to read. This includes reading the process environment which potentially includes sensitive information, such as secrets. Furthermore, an attacker could leverage this vulnerability to use the Pulsar Functions Worker as a proxy to access the content of remote HTTP and HTTPS endpoint URLs. This could also be used to carry out denial of service attacks.
This vulnerability also applies to the Pulsar Broker when it is configured with &amp;#34;functionsWorkerEnabled=true&amp;#34;.&lt;/p&gt;
&lt;p&gt;This issue affects Apache Pulsar versions from 2.4.0 to 2.10.5, from 2.11.0 to 2.11.3, from 3.0.0 to 3.0.2, from 3.1.0 to 3.1.2, and 3.2.0.&lt;/p&gt;
&lt;p&gt;2.10 Pulsar Function Worker users should upgrade to at least 2.10.6.
2.11 Pulsar Function Worker users should upgrade to at least 2.11.4.
3.0 Pulsar Function Worker users should upgrade to at least 3.0.3.
3.1 Pulsar Function Worker users should upgrade to at least 3.1.3.
3.2 Pulsar Function Worker users should upgrade to at least 3.2.1.&lt;/p&gt;
&lt;p&gt;Users op…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-c2x9-vw5h-39vc</guid>
    </item>
    <item>
      <title>gsd-2024-27894</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-27894</link>
      <description>gsd-2024-27894</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-27894</guid>
    </item>
  </channel>
</rss>
