Vulnerability	Vulnerable Version
M Security Bypass Affected versions of `pyjwt` are vulnerable to Security Bypass. when `alg=none` its accept value for the key which could bypass signature verification. How to fix Security Bypass? Upgrade `pyjwt` to version 1.0.0 or higher.	[,1.0.0)
H Authentication Bypass `pyjwt` is a JSON Web Token implementation in Python. Affected versions of the package are vulnerable to Authentication Bypass. In PyJWT 1.5.0 and below the `invalid_strings` check in `HMACAlgorithm.prepare_key` does not account for all PEM encoded public keys. Specifically, the PKCS1 PEM encoded format would be allowed because it is prefaced with the string `-----BEGIN RSA PUBLIC KEY-----` which is not accounted for. This enables symmetric/asymmetric key confusion attacks against users using the PKCS1 PEM encoded public keys, which would allow an attacker to craft JWTs from scratch. How to fix Authentication Bypass? Upgrade `pyjwt` to version 1.5.1 or higher.	[,1.5.1)

Security Bypass

Affected versions of pyjwt are vulnerable to Security Bypass.

when alg=none its accept value for the key which could bypass signature verification.

How to fix Security Bypass?

Upgrade pyjwt to version 1.0.0 or higher.

[,1.0.0)

Authentication Bypass

pyjwt is a JSON Web Token implementation in Python.

Affected versions of the package are vulnerable to Authentication Bypass. In PyJWT 1.5.0 and below the invalid_strings check in HMACAlgorithm.prepare_key does not account for all PEM encoded public keys. Specifically, the PKCS1 PEM encoded format would be allowed because it is prefaced with the string -----BEGIN RSA PUBLIC KEY----- which is not accounted for. This enables symmetric/asymmetric key confusion attacks against users using the PKCS1 PEM encoded public keys, which would allow an attacker to craft JWTs from scratch.

How to fix Authentication Bypass?

Upgrade pyjwt to version 1.5.1 or higher.

[,1.5.1)

Go back to all versions of this package