https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 22 Oct 2026 08:13:41 +0000 https://db.gcve.eu/vuln/fkie_cve-2026-105935 <p>The Pulsar Functions Worker provides a REST API endpoint for triggering a function, which publishes a caller-supplied value to one of the function&#39;s configured input topics. The Functions Worker performs this publish with its own broker client, which authenticates with the Worker&#39;s configured broker-client credentials rather than the credentials of the API caller.</p> <p>When authorization is enabled, in Apache Pulsar 2.4.0 and later versions, the trigger endpoint checks only that the caller is authorized to perform function operations in the function&#39;s namespace. It does not check that the caller is authorized to produce to the input topic that the message is published to. Versions before 2.4.0 do not perform a caller authorization check for the trigger endpoint at all. Function input topics are not restricted to the function&#39;s own tenant or namespace, and registering a function does not require produce permission on its input topics.</p> <p>As a result, an authenticated user who is authorized to manage functions in a namespace, for example a role granted the functions permission on that namespace, can cause the Functions Worker to publish messages with caller-controlled content to a topic that the user is not authorized to produce to, including topics in other tenants. These messages are published under the identity of the Functions Worker. The issue does not require any function instance to be running or any function code to be executed. It requires that the Functions Worker&#39;s broker…</p> <p>The Pulsar Functions Worker provides a REST API endpoint for triggering a function, which publishes a caller-supplied value to one of the function&#39;s configured input topics. The Functions Worker performs this publish with its own broker client, which authenticates with the Worker&#39;s configured broker-client credentials rather than the credentials of the API caller.</p> <p>When authorization is enabled, in Apache Pulsar 2.4.0 and later versions, the trigger endpoint checks only that the caller is authorized to perform function operations in the function&#39;s namespace. It does not check that the caller is authorized to produce to the input topic that the message is published to. Versions before 2.4.0 do not perform a caller authorization check for the trigger endpoint at all. Function input topics are not restricted to the function&#39;s own tenant or namespace, and registering a function does not require produce permission on its input topics.</p> <p>As a result, an authenticated user who is authorized to manage functions in a namespace, for example a role granted the functions permission on that namespace, can cause the Functions Worker to publish messages with caller-controlled content to a topic that the user is not authorized to produce to, including topics in other tenants. These messages are published under the identity of the Functions Worker. The issue does not require any function instance to be running or any function code to be executed. It requires that the Functions Worker&#39;s broker…</p> https://db.gcve.eu/vuln/fkie_cve-2026-105935 https://db.gcve.eu/vuln/ghsa-7w25-m888-8hcq <p>The Pulsar Functions Worker provides a REST API endpoint for triggering a function, which publishes a caller-supplied value to one of the function&#39;s configured input topics. The Functions Worker performs this publish with its own broker client, which authenticates with the Worker&#39;s configured broker-client credentials rather than the credentials of the API caller.</p> <p>When authorization is enabled, in Apache Pulsar 2.4.0 and later versions, the trigger endpoint checks only that the caller is authorized to perform function operations in the function&#39;s namespace. It does not check that the caller is authorized to produce to the input topic that the message is published to. Versions before 2.4.0 do not perform a caller authorization check for the trigger endpoint at all. Function input topics are not restricted to the function&#39;s own tenant or namespace, and registering a function does not require produce permission on its input topics.</p> <p>As a result, an authenticated user who is authorized to manage functions in a namespace, for example a role granted the functions permission on that namespace, can cause the Functions Worker to publish messages with caller-controlled content to a topic that the user is not authorized to produce to, including topics in other tenants. These messages are published under the identity of the Functions Worker. The issue does not require any function instance to be running or any function code to be executed. It requires that the Functions Worker&#39;s broker…</p> <p>The Pulsar Functions Worker provides a REST API endpoint for triggering a function, which publishes a caller-supplied value to one of the function&#39;s configured input topics. The Functions Worker performs this publish with its own broker client, which authenticates with the Worker&#39;s configured broker-client credentials rather than the credentials of the API caller.</p> <p>When authorization is enabled, in Apache Pulsar 2.4.0 and later versions, the trigger endpoint checks only that the caller is authorized to perform function operations in the function&#39;s namespace. It does not check that the caller is authorized to produce to the input topic that the message is published to. Versions before 2.4.0 do not perform a caller authorization check for the trigger endpoint at all. Function input topics are not restricted to the function&#39;s own tenant or namespace, and registering a function does not require produce permission on its input topics.</p> <p>As a result, an authenticated user who is authorized to manage functions in a namespace, for example a role granted the functions permission on that namespace, can cause the Functions Worker to publish messages with caller-controlled content to a topic that the user is not authorized to produce to, including topics in other tenants. These messages are published under the identity of the Functions Worker. The issue does not require any function instance to be running or any function code to be executed. It requires that the Functions Worker&#39;s broker…</p> https://db.gcve.eu/vuln/ghsa-7w25-m888-8hcq