Skip to main content
No exploitation reportedFix available

CVE-2021-41571

No exploitation reported by the sources we read.

  • Published2022-02-01
  • Fixed in2.7.3 · 2.6.4
  • WeaknessCWE-863

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

In Apache Pulsar it is possible to access data from BookKeeper that does not belong to the topics accessible by the authenticated user. The Admin API get-message-by-id requires the user to input a topic and a ledger id. The ledger id is a pointer to the data, and it is supposed to be a valid it for the topic. Authorisation controls are performed against the topic name and there is not proper validation the that ledger id is valid in the context of such ledger. So it may happen that the user is able to read from a ledger that contains data owned by another tenant. This issue affects Apache Pulsar Apache Pulsar version 2.8.0 and prior versions; Apache Pulsar version 2.7.3 and prior versions; Apache Pulsar version 2.6.4 and prior versions.

Timeline

dates in UTC
  1. 2022-02-0113:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2021-41571?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2021-41571?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD · OSV
Apache pulsar
BranchAffectedFixed in
2.7≥ 2.7.0, < 2.7.32.7.3
2.6≥ 2.6.0, < 2.6.42.6.4
2.8= 2.8.0no fix published
pulsar
BranchAffectedFixed in
2.8≥ 2.8.0, < 2.8.12.8.1
2.7≥ 2.7.0, < 2.7.42.7.4
2.6≤ 2.6.4no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • CVE-2021-41571 Red Hat Product Security1 known affected

    pulsar: Pulsar Admin API allows access to data from other tenants using getMessageById API

    pulsar-client-admin as a component of Red Hat Integration Camel K 1

Full record on NVD

Fix

  1. Update Apache pulsar to 2.7.3 · 2.6.4
  2. No fix available, says the vendor Red Hat Product Security CVE-2021-41571 · 1 productAffected

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • NVDCVSS 3.16.5read 2026-10-23
  • NVDCVSS 2.04read 2026-10-23
  • CNAweakness (CWE)CWE-863read 2026-10-23
  • NVDweakness (CWE)CWE-863read 2026-10-23
  • FIRST EPSSEPSS score1.7 %2026-10-23
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Published
2022-02-01
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2021-41571?

In Apache Pulsar it is possible to access data from BookKeeper that does not belong to the topics accessible by the authenticated user. The Admin API get-message-by-id requires the user to input a topic and a ledger id. The ledger id is a pointer to the data, and it is supposed to be a valid it for the topic. Authorisation controls are performed against the topic name and there is not proper validation the that ledger id is valid in the context of such ledger. So it may happen that the user is able to read from a ledger that contains data owned by another tenant. This issue affects Apache Pulsar Apache Pulsar version 2.8.0 and prior versions; Apache Pulsar version 2.7.3 and prior versions; Apache Pulsar version 2.6.4 and prior versions.

Is CVE-2021-41571 actively exploited?

Active exploitation of CVE-2021-41571 has not been confirmed. Its EPSS score was 1.7% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2021-41571?

CVE-2021-41571 has a CVSS v3 base score of 6.5 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.

Running pulsar? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month