https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 22 Oct 2026 15:53:20 +0000 https://db.gcve.eu/vuln/cve-2026-105934 <p><strong>Affected:</strong> Apache Software Foundation Apache Pulsar</p> <p>The Apache Pulsar broker admin REST API provides a truncate operation for persistent topics (DELETE /admin/v2/persistent/{tenant}/{namespace}/{topic}/truncate). Truncating a topic moves all subscription cursors of the topic to the end of the topic and deletes the topic&#39;s inactive ledgers. Truncating a non-partitioned topic, or a single partition addressed by its partition name, correctly requires the tenant admin role or the superuser role. When the operation is requested for the name of a partitioned topic, the broker does not apply this tenant admin check to the caller. Instead, it truncates each partition using the broker&#39;s own internal admin client, which authenticates with the broker&#39;s configured client credentials rather than the caller&#39;s identity. Each per-partition truncate request is still checked for the tenant admin role or the superuser role, but against the broker&#39;s internal identity instead of the caller. The partitions are therefore truncated only when the broker&#39;s configured client role is a superuser or an admin of the target tenant, which is the usual configuration when authorization is enabled.</p> <p>As a result, when that condition holds, an authenticated user who is not a tenant admin can truncate any partitioned topic on which the user has lookup permission. Caller authentication and lookup permission alone are not sufficient: if the broker&#39;s internal identity lacks tenant admin or superuser authorization for the target tenant, the per-partition requests are…</p> <p><strong>Affected:</strong> Apache Software Foundation Apache Pulsar</p> <p>The Apache Pulsar broker admin REST API provides a truncate operation for persistent topics (DELETE /admin/v2/persistent/{tenant}/{namespace}/{topic}/truncate). Truncating a topic moves all subscription cursors of the topic to the end of the topic and deletes the topic&#39;s inactive ledgers. Truncating a non-partitioned topic, or a single partition addressed by its partition name, correctly requires the tenant admin role or the superuser role. When the operation is requested for the name of a partitioned topic, the broker does not apply this tenant admin check to the caller. Instead, it truncates each partition using the broker&#39;s own internal admin client, which authenticates with the broker&#39;s configured client credentials rather than the caller&#39;s identity. Each per-partition truncate request is still checked for the tenant admin role or the superuser role, but against the broker&#39;s internal identity instead of the caller. The partitions are therefore truncated only when the broker&#39;s configured client role is a superuser or an admin of the target tenant, which is the usual configuration when authorization is enabled.</p> <p>As a result, when that condition holds, an authenticated user who is not a tenant admin can truncate any partitioned topic on which the user has lookup permission. Caller authentication and lookup permission alone are not sufficient: if the broker&#39;s internal identity lacks tenant admin or superuser authorization for the target tenant, the per-partition requests are…</p> https://db.gcve.eu/vuln/cve-2026-105934