Skip to main content
Vulnerability Database/CVE-2026-105930

CVE-2026-105930: Apache Pulsar Information Disclosure

CVE-2026-105930 is an information disclosure flaw in Apache Pulsar that allows unauthorized access to package contents across tenants. This article covers technical details, affected versions, and patching steps.

Published:

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-105930 Overview

CVE-2026-105930 is a broken authorization vulnerability [CWE-863] in Apache Pulsar's Functions worker. When package management is enabled, the worker authorizes package URL requests only against the destination namespace of the component being registered or updated. It does not verify that the requesting user holds the packages permission on the namespace referenced by the package URL. The worker also retrieves the package from the broker using its own credentials, bypassing the caller's identity.

An authenticated tenant user permitted to register functions, sources, or sinks can read package contents from namespaces in other tenants. Disclosed contents may include application code, business logic, and embedded credentials.

Critical Impact

Cross-tenant disclosure of package contents, including application code and embedded credentials, through authorized Function, Source, or Sink registration APIs.

Affected Products

  • Apache Pulsar 2.8.0 through versions before 4.0.14
  • Apache Pulsar 4.1.0 through 4.1.3
  • Apache Pulsar 4.2.0 through versions before 4.2.5

Discovery Timeline

  • 2026-10-21 - CVE-2026-105930 published to NVD
  • 2026-10-22 - Last updated in NVD database

Technical Details for CVE-2026-105930

Vulnerability Analysis

Apache Pulsar supports a Packages Management Service that stores reusable artifacts referenced by package://tenant/namespace/package@version URLs. The Functions worker accepts these URLs when a user registers or updates a Function, Source, or Sink, and also when a transform function is supplied for a Sink.

The worker performs an authorization check for the destination namespace of the new component. It then calls the broker to fetch the package referenced by the URL. That fetch uses the worker's service credentials rather than the caller's identity, and no additional check is made against the source namespace of the package URL.

A tenant user with permission to create or update components in their own namespace can therefore supply a package URL pointing at another tenant's namespace. The worker retrieves the package and makes its contents available during component deployment. The flaw affects confidentiality only; packages cannot be modified or deleted and availability is not affected.

Root Cause

The root cause is a missing authorization check on the package source namespace combined with privilege confusion between the worker service account and the end user. The permission check of the Packages Management Service runs against the worker's identity instead of the requesting user's, satisfying [CWE-863] Incorrect Authorization.

Attack Vector

Exploitation requires an authenticated account with permission to register or update Functions, Sources, or Sinks in any namespace of the attacker's own tenant. The attacker submits a create or update request that references a package:// URL targeting a victim tenant namespace. The vulnerability only affects deployments where authentication and authorization are enabled and both enablePackagesManagement on the broker and functionsWorkerEnablePackageManagement on the Functions worker are turned on. Both settings are disabled by default.

The vulnerability mechanism is described in prose; no verified proof-of-concept code is published. See the Apache Pulsar CVE-2026-105930 advisory for additional technical detail.

Detection Methods for CVE-2026-105930

Indicators of Compromise

  • Function, Source, or Sink registration or update requests whose package:// URL namespace differs from the destination namespace of the component.
  • Broker package download events attributed to the Functions worker service identity shortly after a tenant user API call.
  • Unexpected cross-tenant access patterns in Pulsar Packages Management Service audit logs.

Detection Strategies

  • Review Functions worker and broker access logs for admin/v3/functions, admin/v3/sources, and admin/v3/sinks requests that include a package:// URL referencing a foreign tenant or namespace.
  • Correlate the requesting user identity with the tenant and namespace component of the submitted package URL to flag mismatches.
  • Alert when a single tenant principal references package URLs across multiple distinct tenants within a short window.

Monitoring Recommendations

  • Enable detailed audit logging on the Pulsar broker and Functions worker, and forward it to a centralized analytics platform for retention and correlation.
  • Monitor the Packages Management API for read operations initiated by the worker's service identity and reconcile them against the originating user request.
  • Baseline normal package reference patterns per tenant and alert on deviations such as new foreign-tenant references.

How to Mitigate CVE-2026-105930

Immediate Actions Required

  • Upgrade Apache Pulsar 4.0.x deployments to at least 4.0.14.
  • Upgrade Apache Pulsar 4.1.x and 4.2.x deployments to at least 4.2.5.
  • Inventory existing packages for embedded credentials and rotate any secrets that could have been exposed through cross-tenant reads.
  • Audit historical Functions, Sources, and Sinks registration events for suspicious cross-tenant package:// references.

Patch Information

Apache Pulsar fixed this issue in versions 4.0.14 and 4.2.5. The supported release lines are 4.0.x and 5.0.x per the Apache Pulsar release policy. Deployments on unsupported lines should move to a supported, patched release. Full details are in the Apache Pulsar CVE-2026-105930 advisory and the Apache List Discussion.

Workarounds

  • Disable package management by setting enablePackagesManagement=false on the broker and functionsWorkerEnablePackageManagement=false on the Functions worker if the feature is not required.
  • Restrict permissions to create or update Functions, Sources, and Sinks to a minimal set of trusted principals until patches are applied.
  • Avoid embedding secrets or credentials in packaged artifacts; load secrets from an external secret manager at runtime.
bash
# Configuration example: disable package management until patched
# broker.conf
enablePackagesManagement=false

# functions_worker.yml
functionsWorkerEnablePackageManagement: false

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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.