Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-105945 Overview
CVE-2026-105945 is a path traversal vulnerability [CWE-22] in the Apache Pulsar Packages Management Service. The flaw exists in the filesystem storage provider (FileSystemPackagesStorageProvider), where the version component of a package name is not validated. An authenticated user with the packages permission on any namespace can supply URL-encoded path separators and parent directory references in the version field to access packages belonging to other tenants or namespaces. The vulnerability affects Apache Pulsar versions 2.10.0 through 4.0.13 and 4.1.0 through 4.2.4.
Critical Impact
Authenticated attackers can download, overwrite, or delete packages across tenant boundaries, affecting the integrity and availability of Pulsar Functions, Sources, and Sinks that consume those packages.
Affected Products
- Apache Pulsar versions 2.10.0 before 4.0.14
- Apache Pulsar versions 4.1.0 before 4.2.5
- Deployments using enablePackagesManagement with FileSystemPackagesStorageProvider
Discovery Timeline
- 2026-10-21 - CVE-2026-105945 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-105945
Vulnerability Analysis
The Pulsar Packages Management Service identifies packages using a composite name made of type, tenant, namespace, name, and version. Authorization checks evaluate only the tenant and namespace components. The filesystem storage path, however, is derived from all five components, including the untrusted version string.
Because the version component is not sanitized, an authenticated user can embed URL-encoded path traversal sequences such as %2F and %2E%2E in the version field. The filesystem storage provider resolves the manipulated path to a location belonging to a different tenant or namespace. The containment check implemented in recent releases does not catch this traversal, because the resolved path still falls inside the configured storage root directory.
Root Cause
The root cause is missing input validation on the version component of a package name combined with authorization decisions that ignore that component. The containment check verifies only that the final path stays inside the storage directory. It does not verify that the path remains within the tenant and namespace subtree that authorization approved.
Attack Vector
An attacker authenticates to the broker's admin REST API with packages permission on any single namespace. The attacker then issues package download, upload, or delete requests specifying a crafted version string containing URL-encoded directory traversal sequences. The filesystem storage provider resolves these to arbitrary package files owned by other tenants. If authentication is disabled on the broker, any network-reachable client can perform these operations. Overwritten or deleted packages consumed by Pulsar Functions, Sources, or Sinks can disrupt processing pipelines or introduce attacker-controlled code into those runtimes.
Detection Methods for CVE-2026-105945
Indicators of Compromise
- Admin REST API requests to /admin/v3/packages/ endpoints containing URL-encoded sequences such as %2F, %2E%2E, or %2E%2E%2F in the version path segment.
- Unexpected modifications, deletions, or downloads of package files in the directory configured by packagesManagementStorageProvider.
- Pulsar Functions, Sources, or Sinks failing to load or exhibiting unexpected behavior after package store changes.
Detection Strategies
- Enable broker access logging and search for package management API calls where the version component contains percent-encoded characters.
- Audit filesystem access patterns on the broker package storage directory for cross-tenant writes or deletions.
- Correlate package upload or delete events with the authenticated principal's authorized tenant and namespace scope.
Monitoring Recommendations
- Monitor broker logs for HTTP 2xx responses to package operations where the request path contains traversal patterns.
- Alert on package operations performed by principals whose permitted namespaces do not match the affected package location.
- Track changes to package artifacts referenced by active Functions, Sources, and Sinks for unexpected churn.
How to Mitigate CVE-2026-105945
Immediate Actions Required
- Upgrade Apache Pulsar 4.0.x deployments to 4.0.14 or later.
- Upgrade Apache Pulsar 4.1.x and 4.2.x deployments to 4.2.5 or later.
- Verify that broker authentication and authorization are enabled, and restrict packages permissions to trusted principals.
- Review package storage directories for signs of cross-tenant tampering before and after patching.
Patch Information
Apache has released fixed versions in 4.0.14 and 4.2.5. The currently supported Apache Pulsar release lines are 4.0.x and 5.0.x. Refer to the Apache Pulsar CVE-2026-105945 Advisory and the Apache Mailing List Thread for complete release details.
Workarounds
- Disable the Packages Management Service by setting enablePackagesManagement=false in broker.conf if the feature is not required.
- Switch packagesManagementStorageProvider from the filesystem provider to the default Apache BookKeeper-based provider, which is not affected.
- Ensure the broker's admin REST API is not exposed to untrusted networks and that authentication is enforced.
# broker.conf - disable packages management if unused
enablePackagesManagement=false
# Or switch to the unaffected BookKeeper-backed storage provider
packagesManagementStorageProvider=org.apache.pulsar.packages.management.storage.bookkeeper.BookKeeperPackagesStorageProvider
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

