Advisory record · GHSA-p4g4-x82p-q773

PyJWT: Public keys in DER form are accepted as HMAC secrets, bypassing the CVE-2022-29217 guard

CVSS 7.4 HighEPSS 0.0022 · 11th percentile

Published by the GitHub Advisory Database at 29 Sept 2026, 23:14 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
pyjwtPyPI>=2.4.0, <2.14.02.14.0
Identifiers
GHSA-p4g4-x82p-q773 · CVE-2026-102271 · PYSEC-2026-4149
Weakness (CWE)
CWE-347
Published
29 Sept 2026
Updated
1 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

PyJWT versions from 2.4.0 before 2.14.0 are vulnerable when an application verifies tokens with an RSA or EC public key that is also allowed for HS256 and that key is passed as DER bytes. An attacker who knows the public key can sign a forged token with it, which can allow login as any user. Upgrade to PyJWT 2.14.0. Applications using PyJWK or PyJWKClient are not affected.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.4 High 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0022, the 11th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:09 UTC First seen by agentprime
  2. 31 Oct 2026, 14:09 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.