Which products and versions are affected by CVE-2021-22160?

Affected: Pulsar (Apache) versions >= Apache Pulsar; org.apache.pulsar:pulsar (maven). The full list is in the CVE brief.

Is CVE-2021-22160 being exploited in the wild?

It is not listed in any known-exploited vulnerabilities catalog.

Is CVE-2021-22160 in the CISA KEV catalog?

No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.

Is there a public exploit for CVE-2021-22160?

No public exploit code is known.

Is there a fix for CVE-2021-22160?

Fixed versions are available, including Pulsar 2.7.1, org.apache.pulsar:pulsar 2.7.2.

How urgently should CVE-2021-22160 be patched?

Brandefense priority: patch immediately, because it is very likely to be exploited soon.

Request A Demo

Vulnerability Intelligence

CVE-2021-22160

Critical

Improper Verification of Cryptographic Signature in Apache Pulsar in TensorFlow

Published Jun 1, 2021 · Updated Jul 9, 2026 · Also known as GHSA-3cv4-xxv7-934q

Key Facts

Patch immediately

CVE-2021-22160 is a critical-severity vulnerability (CVSS 9.8 v3.1) affecting Pulsar (Apache), org.apache.pulsar:pulsar (maven).
It is not listed in any known-exploited vulnerabilities catalog. No public exploit code is known.
EPSS estimates a 53% probability of exploitation in the next 30 days.
Fixed versions are available, including Pulsar 2.7.1, org.apache.pulsar:pulsar 2.7.2.
Brandefense priority: patch immediately, because it is very likely to be exploited soon.

CVSS v3.1

9.8

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS (30-day exploit likelihood)

53%

Higher than 98.9% of all scored CVEs

Exploited in the wild

No known

Not in a known-exploited catalog

Public exploit code

None known

Get the full CVE-2021-22160 brief as a PDF

Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.

Description

If Apache Pulsar is configured to authenticate clients using tokens based on JSON Web Tokens (JWT), the signature of the token is not validated if the algorithm of the presented token is set to "none". This allows an attacker to connect to Pulsar instances as any user (incl. admins).

Affected Products

3 affected entries in total

Product	Affected versions	Fixed in
PulsarApache	>= Apache Pulsar	2.7.1
org.apache.pulsar:pulsarmaven	See advisory	2.7.2

Patched Releases

Pulsar

2.7.1

org.apache.pulsar:pulsar

2.7.2

Timeline

Publicly disclosed
Jun 1, 2021
Last updated
Jul 9, 2026

Weakness Type

CWE-347 Improper Verification of Cryptographic Signature

References

15 more references in the full CVE brief

FAQ

Common Questions.

If Apache Pulsar is configured to authenticate clients using tokens based on JSON Web Tokens (JWT), the signature of the token is not validated if the algorithm of the presented token is set to "none".
Affected: Pulsar (Apache) versions >= Apache Pulsar; org.apache.pulsar:pulsar (maven). The full list is in the CVE brief.
It is not listed in any known-exploited vulnerabilities catalog.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
No public exploit code is known.
Fixed versions are available, including Pulsar 2.7.1, org.apache.pulsar:pulsar 2.7.2.
Brandefense priority: patch immediately, because it is very likely to be exploited soon.

Is CVE-2021-22160 Running On Your Attack Surface?

Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.