CVE-2026-105869: Flaw in Apache Pulsar Scores 9.2 on CVSS
A newly published critical vulnerability in Apache Pulsar carries a CVSS score of 9.2. Here is what is affected and how to respond.
Key points
- CVE-2026-105869 affects Apache Pulsar.
- CVSS 9.2 (Critical).
- No exploitation confirmed yet.
Apache Pulsar is affected by CVE-2026-105869, a security flaw that the National Vulnerability Database rates 9.2 out of 10.
At a glance
- CVE
- CVE-2026-105869
- Product
- Apache Pulsar
- CVSS
- 9.2 Critical
- Weakness
- CWE-347
- Exploited
- No known exploitation
What is the vulnerability?
The NVD entry states: Apache Pulsar's MultiRolesTokenAuthorizationProvider authorizes a client with all roles listed in a claim of its JSON Web Token (JWT). The provider is intended for use with token authentication, which verifies the token before authorization. The provider did not verify the token itself: it parsed the token's claims with the signature removed and trusted that authentication had already checked it.
When authentication and authorization are enabled with a non-empty anonymousUserRole setting, some HTTP requests whose credentials fail authentication are not rejected, but are handled as requests of the anonymous user role. For the broker's HTTP endpoints, such as the admin REST API, this fallback applies to requests that do not name an authentication method and requires strictAuthMethod to be false (the default) where that setting is available. For the WebSocket API, failed credentials can al
Affected versions
| Vendor | Product | Versions |
|---|---|---|
| Apache Software Foundation | Apache Pulsar | before 4.0.14, before 4.2.5 |
Is it being exploited?
There is no public confirmation of exploitation at the time of publication. It does not appear in CISA's Known Exploited Vulnerabilities catalog. We will update this report if that changes.
What should you do?
- Identify whether the affected product and versions run in your environment.
- Apply the vendor update listed in the advisory as soon as it is available.
- Limit network exposure of the affected service until it is patched.
- Monitor the vendor advisory for updated guidance or exploitation reports.
What to do and how to stay safe: CVE-2026-105869
- Vulnerability severity scores ignore your specific architecture and context.
- Exploitability depends on network exposure and user behavior, not just code flaws.
- Prioritization requires continuous asset inventory and threat intelligence alignment.
Risk-based vulnerability management focuses your limited resources on the flaws that actually threaten your business. Start by mapping your critical assets and checking for active exploits to prioritize your backlog.
Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is CVE-2026-105869?
CVE-2026-105869 is a CWE-347 vulnerability in Apache Pulsar.
How severe is CVE-2026-105869?
It has a CVSS score of 9.2 Critical.
Is CVE-2026-105869 being exploited?
There is no public confirmation of exploitation at the time of publication.
