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-105927 Overview
Apache Pulsar contains an authorization flaw in its WebSocket service that allows authenticated consumers to inject messages into topics they do not own. The WebSocket consumer endpoint accepts a deadLetterTopic query parameter but only verifies CONSUME permission on the subscribed topic. It does not verify PRODUCE permission on the dead letter target. The WebSocket service writes dead letter messages using its own broker client identity, enabling cross-tenant message injection into any existing namespace. The flaw is tracked under CWE-863 (Incorrect Authorization).
Critical Impact
Any authenticated user with CONSUME permission on a single topic can write arbitrary messages to topics in other tenants' namespaces when the WebSocket service is enabled.
Affected Products
- Apache Pulsar 2.3.0 through versions before 4.0.14
- Apache Pulsar 4.1.0 through versions before 4.2.5
- Apache Pulsar deployments with WebSocket service enabled (webSocketServiceEnabled) or standalone WebSocket proxy
Discovery Timeline
- 2026-10-21 - CVE-2026-105927 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-105927
Vulnerability Analysis
The Apache Pulsar WebSocket service exposes a consumer endpoint that accepts dead letter policy configuration through query parameters. The deadLetterTopic parameter specifies the destination for messages that exceed the maximum redelivery count. When authorization is enabled, the service validates that the connecting user holds CONSUME permission on the subscribed topic but omits any permission check against the dead letter destination.
The WebSocket service then creates a producer for the dead letter topic using its own broker client identity rather than the connecting user's identity. This identity substitution bypasses tenant isolation. An attacker who directly attempts to produce to the target topic is correctly refused, but routing the write through the WebSocket dead letter mechanism succeeds.
When automatic topic creation is enabled, which is the default configuration, the named topic is created on demand. Attackers can therefore inject messages into topics they name arbitrarily within any accessible namespace. The user controls injected message content when they also control messages on the subscribed topic that trigger redelivery.
Root Cause
The root cause is incomplete authorization enforcement in the WebSocket consumer endpoint. The service performs a single permission check scoped to the subscription operation and inherits the WebSocket proxy's broker credentials for all downstream produce operations. Dead letter producers register no schema, so the write succeeds against any topic unless schema validation is explicitly enforced for the target namespace, which is not the default.
Attack Vector
The attack requires network access to the WebSocket service, valid authentication, and CONSUME permission on at least one topic. The attacker connects as a WebSocket consumer, specifies a dead letter topic in a different tenant's namespace, and arranges for the maximum redelivery count to be exceeded on the subscribed topic. The WebSocket service then produces the message to the attacker-chosen topic under its own identity.
Injected messages carry dead letter message properties and a dead letter producer name, but these values are not authenticated. Repeated injection consumes storage and backlog capacity in the target namespace, creating a secondary resource exhaustion impact. The vulnerability does not permit reading, modifying, or deleting existing messages. Full technical context is available in the Apache Pulsar security advisory.
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 AttacksDetection Methods for CVE-2026-105927
Indicators of Compromise
- Pulsar topics containing messages with dead letter message properties and a dead letter producer name that do not correspond to legitimate dead letter workflows configured by namespace owners.
- Unexpected topic creation events in namespaces where WebSocket client access was not authorized, particularly when allowAutoTopicCreation is enabled.
- WebSocket consumer connections specifying deadLetterTopic query parameters targeting topics outside the subscribed namespace or tenant.
Detection Strategies
- Audit broker logs for producer registrations originating from the WebSocket service role against topics owned by tenants other than the connecting user's tenant.
- Correlate WebSocket consumer endpoint access logs with the deadLetterTopic query parameter values and compare against the authenticated principal's permitted produce scope.
- Review message metadata in sensitive topics for dead letter properties that were not generated by expected application subscriptions.
Monitoring Recommendations
- Enable verbose authorization logging on brokers to capture produce operations performed under the WebSocket service identity.
- Monitor namespace-level backlog and storage growth for anomalous spikes indicative of injection-driven resource consumption.
- Track topic auto-creation events and alert when topics appear in namespaces that have no active legitimate producers.
How to Mitigate CVE-2026-105927
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.
- Disable the WebSocket service by setting webSocketServiceEnabled=false on brokers and shutting down any standalone WebSocket proxies if the service is not required.
- Audit historical broker logs for prior dead letter producer activity targeting topics across tenant boundaries.
Patch Information
Apache Pulsar released fixes in versions 4.0.14 and 4.2.5. The currently supported release lines are 4.0.x and 5.0.x, as documented in the Apache Pulsar release policy. Users on versions older than 4.0.x should upgrade directly to a supported patched release. Patch details are available on the Apache Pulsar security page and in the Apache mailing list announcement.
Workarounds
- Restrict network access to the WebSocket service so that only trusted clients can reach the consumer endpoint.
- Limit the broker-side permissions granted to the role that the WebSocket service uses so it can only produce to namespaces WebSocket clients are intended to access.
- Enable schema validation enforcement on sensitive namespaces, which rejects the schema-less producer that the WebSocket dead letter mechanism creates.
- Disable allowAutoTopicCreation at the broker or namespace level to prevent attackers from materializing arbitrary topic names.
# Configuration example: disable the WebSocket service on brokers
# in conf/broker.conf
webSocketServiceEnabled=false
# Restrict automatic topic creation at broker scope
allowAutoTopicCreation=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

