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

CVE-2026-105932: Apache Pulsar Auth Bypass Vulnerability

CVE-2026-105932 is an authentication bypass flaw in Apache Pulsar that allows unauthorized users to modify non-persistent topic entry filter policies. This post explains its impact, affected versions, and mitigation 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-105932 Overview

CVE-2026-105932 is a missing authorization flaw [CWE-862] in the Apache Pulsar broker admin REST API. The endpoints under /admin/v2/non-persistent/{tenant}/{namespace}/{topic}/entryFilters fail to enforce the entry filters topic policy operation check applied to persistent topics. An authenticated user holding only produce or consume permission on a non-persistent topic can read, replace, or remove its topic-level entry filter policy. These operations should be limited to tenant admin or superuser roles. The issue affects Apache Pulsar versions from 3.3.0 before 4.0.14 and from 4.1.0 before 4.2.5.

Critical Impact

Authenticated low-privilege users can tamper with non-persistent topic entry filter policies, altering message dispatch when entry filters are deployed and allowOverrideEntryFilters is enabled.

Affected Products

  • Apache Pulsar 3.3.0 through 4.0.13
  • Apache Pulsar 4.1.0 through 4.2.4
  • Apache Pulsar broker admin REST API (non-persistent topic entry filter endpoints)

Discovery Timeline

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

Technical Details for CVE-2026-105932

Vulnerability Analysis

Apache Pulsar exposes admin REST endpoints that read, set, and remove topic-level entry filter policies. For persistent topics, the handlers invoke the entry filters topic policy authorization check before mutating state. The parallel handlers for non-persistent topics skip this check entirely. The only authorization performed is an indirect lookup permission check that runs when partition metadata is retrieved. Lookup permission is granted to any role with produce or consume rights on the topic or namespace. As a result, callers who should only publish or subscribe can mutate entry filter policy on non-persistent topics.

Practical impact depends on two broker conditions that are not met by default. The operator must install entry filter implementations in the broker's entry filters directory, and allowOverrideEntryFilters must be set to true. When both conditions hold, an unauthorized caller can remove a non-persistent topic's entry filter policy or substitute another installed filter, altering which messages are dispatched to new subscriptions. Because non-persistent topics do not store messages, withheld messages are lost. Existing subscription dispatchers continue to use the entry filters they were created with. Reading the policy discloses only configured filter names; message contents remain protected.

Root Cause

In Pulsar versions before 3.3.0, the entry filters topic policy authorization check lived in code shared by persistent and non-persistent endpoints. Starting in 3.3.0, the check was moved into the persistent-topic path only, leaving the non-persistent handlers without authorization enforcement.

Attack Vector

The attacker must be authenticated and must already hold produce or consume permission on the target non-persistent topic or its namespace. Using any Pulsar admin client or direct HTTP calls to the non-persistent entry filter endpoints, the attacker issues GET, POST, or DELETE requests against the topic's entryFilters policy. The broker returns the current filter configuration, applies a different installed filter, or removes the topic-level policy without rejecting the request.

No verified exploit code examples are published. See the Apache Pulsar CVE-2026-105932 advisory for protocol-level detail.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-105932

Indicators of Compromise

  • Admin REST API requests to /admin/v2/non-persistent/{tenant}/{namespace}/{topic}/entryFilters originating from roles that are not tenant admin or superuser.
  • Unexpected changes in the configured entry filter names on non-persistent topics compared to a known baseline.
  • New subscriptions on non-persistent topics returning message volumes inconsistent with the intended filter policy.

Detection Strategies

  • Enable Pulsar broker access logging for the admin REST API and alert on POST or DELETE requests against non-persistent entryFilters endpoints.
  • Correlate the authenticated role on each entry filter policy request with the expected tenant admin or superuser allowlist.
  • Compare live topic-level entry filter policy state against configuration-as-code baselines on a recurring interval.

Monitoring Recommendations

  • Forward broker admin logs and audit events into a centralized analytics platform for role-based query and alerting.
  • Track allowOverrideEntryFilters broker configuration drift across clusters.
  • Monitor subscription dispatch rates on non-persistent topics for sudden changes that may indicate filter manipulation.

How to Mitigate CVE-2026-105932

Immediate Actions Required

  • Upgrade 3.3.x and 4.0.x deployments to Apache Pulsar 4.0.14 or later.
  • Upgrade 4.1.x and 4.2.x deployments to Apache Pulsar 4.2.5 or later.
  • Audit roles currently granted produce or consume permission on non-persistent topics to confirm least privilege.
  • Review topic-level entry filter policies on non-persistent topics against expected baselines.

Patch Information

The Apache Pulsar project restored the entry filters topic policy authorization check on the non-persistent endpoints. Fixed versions are 4.0.14 on the 4.0.x line and 4.2.5 on the 4.2.x line. The currently supported Pulsar release lines are 4.0.x and 5.0.x per the Apache Pulsar release policy. Full advisory details are published at the Apache Pulsar CVE-2026-105932 advisory.

Workarounds

  • Keep the broker setting allowOverrideEntryFilters at its default value of false so topic-level entry filter policies have no effect on message dispatch.
  • Avoid installing entry filter implementations in the broker's entry filters directory until upgrades are complete, since the policy endpoints can only select from installed filters.
  • Restrict produce and consume grants on sensitive non-persistent topics to trusted roles until patched versions are deployed.
bash
# Configuration example: broker.conf
allowOverrideEntryFilters=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.