CVE-2021-22160 in the critical feed json
Authentication with JWT allows use of “none”-algorithm
published 2021-05-26 5 y ago modified 2026-06-17 4 mo ago also GHSA-3cv4-xxv7-934q , EUVD-2021-1254
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 52.9%
- EPSS 52.9% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
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).
Patch / fix
- maven org.apache.pulsar:pulsar 2.7.2
- Apache Software Foundation Apache Pulsar 2.7.1
Exploit prediction
52.93% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.pulsar:pulsar | <2.7.2 |
2.7.2 |
Affected products
- Apache Software Foundation Apache Pulsar
Classification
- Weakness
-
- CWE-347 Improper Verification of Cryptographic Signature
References
-
lists.apache.org
/thread.html/r347650d15a3e9c5f58b83e918b6ad6dedc2a63d3eb63da8e6a7be87e%40%3Cusers.pulsar.apache.org%3E
web, mailing-list, vendor-advisory
-
lists.apache.org
/thread.html/r9a12b4da2f26ce9b8f7e7117a879efaa973dab7e54717bbc7923fab1%40%3Cdev.pulsar.apache.org%3E
mailing-list, web, vendor-advisory
-
lists.apache.org
/thread.html/rf2e90942996dceebac8296abf39257cfeb5ae918f82f7af3d37a48c5%40%3Cdev.pulsar.apache.org%3E
mailing-list
-
lists.apache.org
/thread.html/ra49cb62105154e4795b259c79a6b27d63bfa2ab5787ff8529b089550%40%3Cdev.pulsar.apache.org%3E
mailing-list
-
lists.apache.org
/thread.html/ra49cb62105154e4795b259c79a6b27d63bfa2ab5787ff8529b089550%40%3Cusers.pulsar.apache.org%3E
mailing-list
-
lists.apache.org
/thread.html/r8e545559781231a83bf0644548c660255859e52feb86bbfcd42590da%40%3Cdev.pulsar.apache.org%3E
mailing-list
-
lists.apache.org
/thread.html/rbe845aa1573a61769b9c5916c62971f4b10de87c2ea5f38a97f0cf84%40%3Cdev.pulsar.apache.org%3E
mailing-list
-
lists.apache.org
/thread.html/rca54f4b26ba5e6f2e39732b47ec51640e89f57e3b6a38ac3bab314df%40%3Cdev.pulsar.apache.org%3E
mailing-list
-
nvd.nist.gov
/vuln/detail/CVE-2021-22160
advisory
-
github.com
/apache/pulsar/releases/tag/v2.7.2
web
-
lists.apache.org
/thread.html/r08c7df60cae031361df7fbac39d08b6d5b5079e74db5195d409db9a2@%3Cdev.pulsar.apache.org%3E
web
-
lists.apache.org
/thread.html/r8e545559781231a83bf0644548c660255859e52feb86bbfcd42590da@%3Cdev.pulsar.apache.org%3E
web
-
lists.apache.org
/thread.html/ra49cb62105154e4795b259c79a6b27d63bfa2ab5787ff8529b089550@%3Cdev.pulsar.apache.org%3E
web
-
lists.apache.org
/thread.html/ra49cb62105154e4795b259c79a6b27d63bfa2ab5787ff8529b089550@%3Cusers.pulsar.apache.org%3E
web
-
lists.apache.org
/thread.html/rbe845aa1573a61769b9c5916c62971f4b10de87c2ea5f38a97f0cf84@%3Cdev.pulsar.apache.org%3E
web
-
lists.apache.org
/thread.html/rca54f4b26ba5e6f2e39732b47ec51640e89f57e3b6a38ac3bab314df@%3Cdev.pulsar.apache.org%3E
web
-
lists.apache.org
/thread.html/re2ae364e0c02093dc721699698c6f23cfbba0220c78b5e28cafeae81@%3Ccommits.pulsar.apache.org%3E
web
-
lists.apache.org
/thread.html/rf2e90942996dceebac8296abf39257cfeb5ae918f82f7af3d37a48c5@%3Cdev.pulsar.apache.org%3E
web
-
lists.apache.org
/thread.html/rf54fefc25c49d4715d484133d438f13bf2e515a5fed5d3a745d4f6e7@%3Ccommits.pulsar.apache.org%3E
web
Sources
- CVE List CVE-2021-22160
- GitHub Advisory GHSA-3cv4-xxv7-934q
- NVD CVE-2021-22160
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.