7 matches found
CVE-2026-105933
Apache Pulsar allows an administrator to require end-to-end message encryption for all topics in a namespace by setting the encryptionrequired namespace policy. When this policy is set, the broker rejects messages that are published without encryption. When the broker loads a persistent topic, it...
EUVD-2026-107470
Apache Pulsar allows an administrator to require end-to-end message encryption for all topics in a namespace by setting the encryptionrequired namespace policy. When this policy is set, the broker rejects messages that are published without encryption. When the broker loads a persistent topic, it...
CVE-2026-105933
Apache Pulsar allows an administrator to require end-to-end message encryption for all topics in a namespace by setting the encryptionrequired namespace policy. When this policy is set, the broker rejects messages that are published without encryption. When the broker loads a persistent topic, it...
CVE-2026-105933 Apache Pulsar: Namespace encryption requirement not enforced after a failure during topic initialization
Apache Pulsar allows an administrator to require end-to-end message encryption for all topics in a namespace by setting the encryptionrequired namespace policy. When this policy is set, the broker rejects messages that are published without encryption. When the broker loads a persistent topic, it...
CVE-2026-105933 Apache Pulsar: Namespace encryption requirement not enforced after a failure during topic initialization
Apache Pulsar allows an administrator to require end-to-end message encryption for all topics in a namespace by setting the encryptionrequired namespace policy. When this policy is set, the broker rejects messages that are published without encryption. When the broker loads a persistent topic, it...
CVE-2026-105933
In Apache Pulsar , a vulnerability exists where the encryption_required namespace policy is not enforced if a failure occurs during topic initialization (e.g., errors reading from the metadata store). Instead of failing the load, the broker logs a warning and proceeds by disabling the encryption ...
Improper Apache Pulsar exception handling vulnerability
A improper exception handling vulnerability exists in Apache Pulsar versions from 1.22.0-incubating up to and including 4.0.14, as well as from 4.1.0 up to and including 4.2.5. This vulnerability arises when initialization steps fail during the loading of persistent topics; as a result, the...