In jsonwebtoken node module before 4.2.2 it is possible for an attacker to bypass verification when a token digitally signed with an asymmetric key (RS/ES family) of algorithms but instead the attacker send a token digitally signed with a symmetric algorithm (HS* family).
https://nodesecurity.io/advisories/17
https://github.com/auth0/node-jsonwebtoken/commit/1bb584bc382295eeb7ee8c4452a673a77a68b687
https://github.com/1nc0gn30/jwt-inspector-guard
https://github.com/alisster00/blueHarbor-VulnLab
https://github.com/clearcapabilities/agentic-security
https://github.com/tierChampion/POC_CVE-2015-9235
https://github.com/z-bool/Venom-JWT
https://www.timmclean.net/2015/02/25/jwt-alg-none.html
https://euvd.enisa.europa.eu/vulnerability/EUVD-2018-0569
https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/