Live › vulnerability › CVE-2026-105930
Go to dashboardWhen package management is enabled, the Pulsar Functions worker fetches packages using its own credentials rather than the requesting user's, so an authenticated user can register or update a function with a package URL pointing to another tenant's namespace and read that package's contents. The impact is disclosure of package contents only; packages cannot be modified or deleted.
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 with authentication and authorization enabled and with package management turned on (broker setting enablePackagesManagement and, in current releases, functionsWorkerEnablePackageManagement) are exposed. Both settings are disabled by default, and clusters that leave package management off can skip this issue.
No product ranges from the sources yet.
enablePackagesManagement and the functions worker setting functionsWorkerEnablePackageManagement; the issue only applies when package management is enabled alongside authentication and authorizationpulsar version, and compare it against the affected ranges: 2.8.0 to before 4.0.14, 4.1.0 through 4.1.3, and 4.2.0 to before 4.2.54.0.144.2.5Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
When package management is enabled, Pulsar Functions, Sources and Sinks can be registered or updated from a package stored in the Pulsar Packages Management Service by supplying a package URL. The Pulsar Functions worker authorized these requests only against the namespace in which the component was being registered or updated. It did not check whether the requesting user was permitted to access packages in the namespace that the package URL refers to, and it retrieved the package from the broker using the worker's own credentials. The permission check of the Packages Management Service was therefore applied to the worker's identity instead of the requesting user's. Package URLs of transform functions supplied when registering or updating a sink were handled in the same way.
An authenticated user who is permitted to register or update functions, sources or sinks in any namespace of their own tenant could use this to obtain the contents of a package stored in a namespace of another tenant, without having the packages permission on that namespace. The impact is limited to disclosure of package contents, which may include application code, business logic or embedded credentials. The issue does not allow packages to be modified or deleted and does not affect availability.
This issue only affects deployments that have authentication and authorization enabled and in which package management has been enabled: the broker setting enablePackagesManagement and, in current releases, the functions worker setting functionsWorkerEnablePackageManagement. Both settings are disabled by default.
This issue affects Apache Pulsar versions from 2.8.0 before 4.0.14, from 4.1.0 through 4.1.3, and from 4.2.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-105930")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.