Live › vulnerability › CVE-2026-105945
Go to dashboardThe Pulsar Packages Management Service with the filesystem storage provider does not validate the package version, so URL-encoded path separators let a request resolve to another tenant's or namespace's package. An authenticated user with packages permission on any namespace can download, overwrite or delete those packages, which can affect Pulsar Functions, Sources and Sinks.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Only deployments that enable package management with the broker setting enablePackagesManagement and use the filesystem storage provider (packagesManagementStorageProvider set to FileSystemPackagesStorageProvider) are exposed. Clusters using the default BookKeeper storage provider or with package management disabled, which is the default, can skip it. Exposure is greatest where authentication is disabled, since any client that can reach the broker admin REST API can use it.
No product ranges from the sources yet.
enablePackagesManagement=true and packagesManagementStorageProvider set to FileSystemPackagesStorageProviderpulsar version; affected are 2.10.0 up to but not including 4.0.14, and 4.1.0 up to but not including 4.2.54.0.144.2.5enablePackagesManagement as an interim measureEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
The Pulsar Packages Management Service can be configured to store packages on the local filesystem of the broker by using the filesystem storage provider. Package names consist of a type, tenant, namespace, name and version. Authorization of package operations is based only on the tenant and namespace, while the storage location of a package is derived from all of these components. The version component of a package name was not validated, so it could contain URL-encoded path separators and parent directory references. The filesystem storage provider resolved such a version to a location belonging to a package in a different tenant or namespace. Because that location is inside the configured storage directory, the containment check that the filesystem storage provider performs in recent releases did not prevent the access.
An authenticated user who has the packages permission on any namespace could use this to download, overwrite or delete packages stored in other tenants or namespaces for which the user has no permission. Packages overwritten or deleted in this way may be used by Pulsar Functions, Sources or Sinks, so the issue can affect the integrity and availability of these components. If authentication is disabled, the operations are available to any client that can reach the broker's admin REST API.
This issue only affects deployments in which package management is enabled with the broker setting enablePackagesManagement and the filesystem storage provider (FileSystemPackagesStorageProvider) is configured with the setting packagesManagementStorageProvider. Package management is disabled by default, and the default storage provider, which stores packages in Apache BookKeeper, is not affected.
This issue affects Apache Pulsar versions from 2.10.0 before 4.0.14 and from 4.1.0 before 4.2.5.
Users operating versions prior to those listed above should upgrade to the aforementioned patched versions or newer versions.
The currently supported Apache Pulsar release lines are 4.0.x and 5.0.x. The supported versions schedule is available at https://pulsar.apache.org/contribute/release-policy/.
This page as .md · .json · in your agent: get_signal("CVE-2026-105945")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.