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-105936 Overview
Apache Pulsar contains a missing authorization flaw [CWE-862] in the Pulsar Functions worker REST API. The deprecated functions connectors endpoint (/admin/v2/functions/connectors and /admin/v3/functions/connectors) returns the installed connector catalog without enforcing the super-user access check applied to the worker connectors endpoint (/admin/v2/worker/connectors). Any authenticated client can read connector metadata regardless of role permissions. The disclosure covers connector names, descriptions, and source, sink, and configuration class names. It does not expose configuration values, credentials, or running connector instances. The issue affects Apache Pulsar versions from 2.4.1 before 4.0.14 and from 4.1.0 before 4.2.5.
Critical Impact
Any authenticated Pulsar client, including low-privileged roles, can enumerate the catalog of installed Pulsar IO connectors through the deprecated functions connectors endpoint when authorization is enabled.
Affected Products
- Apache Pulsar 2.4.1 through 4.0.13
- Apache Pulsar 4.1.0 through 4.1.x
- Apache Pulsar 4.2.0 through 4.2.4
Discovery Timeline
- 2026-10-21 - CVE CVE-2026-105936 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-105936
Vulnerability Analysis
The Pulsar Functions worker exposes two REST endpoints that return the same connector catalog. The worker connectors endpoint at /admin/v2/worker/connectors enforces a super-user access check when authorization is enabled. The deprecated functions connectors endpoints at /admin/v2/functions/connectors and /admin/v3/functions/connectors return the identical data without the authorization check.
The deprecated endpoints are served by both the functions worker and by brokers running the functions worker. This broadens the exposed attack surface across Pulsar deployments that have not disabled the deprecated routes. Unauthenticated requests are rejected unless anonymous access is configured with an anonymous user role.
The returned catalog describes connector type definitions installed in the connectors directory, including the connector name, description, and source, sink, and configuration class names. It does not include configured connector instances, configuration values, or credentials. The presence of an installed connector type does not confirm an active configuration.
Root Cause
The root cause is a missing authorization check [CWE-862] on a deprecated REST endpoint that duplicates functionality from an authorized endpoint. The functions connectors handler fails to apply the super-user access gate used by the worker connectors handler, violating least-privilege expectations.
Attack Vector
An authenticated client sends an HTTP GET request to /admin/v2/functions/connectors or /admin/v3/functions/connectors against a functions worker or broker. The server returns the full connector catalog regardless of the role assigned to the caller. See the Apache Pulsar CVE-2026-105936 Security Advisory for the technical description.
Detection Methods for CVE-2026-105936
Indicators of Compromise
- HTTP GET requests to /admin/v2/functions/connectors or /admin/v3/functions/connectors originating from non-super-user roles.
- Access log entries showing successful 200 responses on the deprecated endpoints following authentication with limited-permission tokens.
- Repeated enumeration of connector endpoints across multiple brokers or workers from the same client identity.
Detection Strategies
- Review Pulsar broker and functions worker access logs for requests to the deprecated functions connectors endpoints and correlate requester roles against expected super-user accounts.
- Enable Pulsar authorization audit logging to attribute REST API calls to specific authenticated identities and surface non-privileged callers hitting administrative routes.
- Add network-layer detections on API gateways or reverse proxies in front of Pulsar to flag paths matching /admin/v*/functions/connectors.
Monitoring Recommendations
- Baseline normal administrative API usage and alert on anomalous callers accessing the connectors catalog endpoints.
- Forward Pulsar REST API access logs to a centralized logging platform and build detections for low-privileged tokens accessing admin paths.
- Track version metadata on all brokers and functions workers to identify unpatched hosts exposing the vulnerable endpoints.
How to Mitigate CVE-2026-105936
Immediate Actions Required
- Upgrade Apache Pulsar 4.0.x deployments to version 4.0.14 or later.
- Upgrade Apache Pulsar 4.1.x and 4.2.x deployments to version 4.2.5 or later.
- Audit role assignments and remove unnecessary authenticated access to functions worker REST APIs.
- Restrict network reachability of the functions worker and broker admin APIs to trusted administrative networks.
Patch Information
Fixed versions apply the same super-user access check to the functions connectors endpoint that already exists on the worker connectors endpoint. Users on 4.0.x should upgrade to at least 4.0.14. Users on 4.1.x or 4.2.x should upgrade to at least 4.2.5. Supported release lines are 4.0.x and 5.0.x per the Apache Pulsar release policy. Additional details are available in the Apache Mailing List Thread.
Workarounds
- Front Pulsar admin APIs with a reverse proxy that blocks requests to /admin/v2/functions/connectors and /admin/v3/functions/connectors for non-administrative callers.
- Direct non-super-user clients to use the built-in sources and sinks endpoints to list available connector types in place of the deprecated routes.
- Verify that anonymous access is disabled unless explicitly required to prevent unauthenticated catalog disclosure.
# Example reverse proxy rule to deny the deprecated endpoints
location ~ ^/admin/v[23]/functions/connectors$ {
return 403;
}
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

