CVE-2026-105945

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. - 4.0.x version users should upgrade to at least 4.0.14. - 4.1.x and 4.2.x version users should upgrade to at least 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/.

• CWE-22

• https://lists.apache.org/thread.html/o5jt8zrg1qxqdrqlb06jjmj4lzydfm2k
• https://pulsar.apache.org/security/CVE-2026-105945/

Published

Oct 21, 2026

Last Modified

Oct 21, 2026

Status

Received

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-105937Apache Pulsar shadow topics (PIP-180) are topics that read t…8.7
• CVE-2026-105938Apache Pulsar namespaces can restrict which roles may use a …2.3
• CVE-2026-10594Rejected reason: This CVE ID has been rejected or withdrawn …
• CVE-2026-105941The Azure Key Vault KMS provider in Kroxylicious accepts an …8.1
• CVE-2026-105942When a configured proxy role sends a request to the broker o…7.7
• CVE-2026-105944Apache Pulsar Manager is a web console for administering Apa…10
• CVE-2026-105949Cruise Control's Jetty ConstraintSecurityHandler registers s…8.8
• CVE-2026-10595A path traversal vulnerability exists in parisneo/lollms ver…7.5
• CVE-2026-105950A security vulnerability has been detected in getformwork fo…3.5
• CVE-2026-105957A vulnerability was detected in SourceCodester Performance I…6.3
• CVE-2026-105958A flaw was found in spice-server. Multiple migration data ha…7.5
• CVE-2026-105959A flaw was found in spice-server. The GLZ encoder dictionary…7.5