Is pyjwt 0.2 vulnerable?
PyPI · 3 releases from 0.2.0 to 0.2.3 · latest pyjwt is 2.15.1 · checked 18 Nov 2026
Yes: 10 known advisories
Yes. pyjwt 0.2.3, the last 0.2 release, is affected by 10 known security advisories (1 critical, 5 high, 3 medium, 1 low), including CVE-2026-102268, CVE-2026-102267, CVE-2026-48526. At least one has no fixed release yet.
Is your project on an affected pyjwt?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting pyjwt 0.2.3
PyJWT: HS256/384/512 verify accepts empty HMAC key via oct JWK (PyJWK/PyJWKClient) enabling token forgery
- Affected
- <2.14.0
- Fixed in
- 2.14.0
PyJWT: ReDoS vulnerability when calling the `is_pem_format` function.
- Affected
- <2.14.0
- Fixed in
- 2.14.0
PyJWT: Non-canonical signature segments enable raw-token revocation bypass
- Affected
- <2.14.0
- Fixed in
- 2.14.0
PyJWT: Asymmetric-PEM detection bypass: whitespace/line-ending-mutated public keys skip the HS/asymmetric confusion guard
- Affected
- <2.14.0
- Fixed in
- 2.14.0
PyJWT: PyJWKClient follows redirects when fetching JWKS
- Affected
- <2.14.0
- Fixed in
- 2.14.0
PyJWT: PyJWKClient still amplifies unauthenticated JWKS fetches on unknown kid values (incomplete fix of CVE-2026-48524)
- Affected
- <2.14.0
- Fixed in
- 2.14.0
PyJWT: Public-key JWK accepted as HMAC secret enables forged HS256 tokens when mixed families are allowed
- Affected
- <2.13.0
- Fixed in
- 2.13.0
PyJWT accepts unknown `crit` header extensions
- Affected
- <2.12.0
- Fixed in
- 2.12.0
No summary published
- Affected
- <=2.10.1
- Fixed in
- No fix released
PyJWT vulnerable to key confusion attacks
- Affected
- <1.5.1
- Fixed in
- 1.5.1
Every pyjwt 0.2.x release
Affected: 0.2.0 to 0.2.3. Latest pyjwt: 2.15.1.
| Version | Known advisories |
|---|---|
| pyjwt 0.2.3 | GHSA-pxh4-856f-4h89, CVE-2026-102270, CVE-2026-102269, CVE-2026-102268, CVE-2026-102267, CVE-2026-101917, CVE-2026-48526, CVE-2026-32597, CVE-2025-45768, CVE-2017-11424 |
| pyjwt 0.2.1 | GHSA-pxh4-856f-4h89, CVE-2026-102270, CVE-2026-102269, CVE-2026-102268, CVE-2026-102267, CVE-2026-101917, CVE-2026-48526, CVE-2026-32597, CVE-2025-45768, CVE-2017-11424 |
| pyjwt 0.2.0 | GHSA-pxh4-856f-4h89, CVE-2026-102270, CVE-2026-102269, CVE-2026-102268, CVE-2026-102267, CVE-2026-101917, CVE-2026-48526, CVE-2026-32597, CVE-2025-45768, CVE-2017-11424 |
Which of your client projects are still on pyjwt 0.2?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact pyjwt version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other pyjwt versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the PyPI registry. Refreshed daily.