Widespread Python JWT library; allows token forgery and auth bypass in many web services—high-impact across organizations and likely to be widely discussed.
CVE-2026-102268
PyJWT token forgery enabling auth bypass (fixed in 2.14.0)
Is CVE-2026-102268 being exploited?
Not confirmed. CVE-2026-102268 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.
How severe is CVE-2026-102268?
CVE-2026-102268 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-102268?
Yes. A fix has been recorded for CVE-2026-102268. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-102268 affect?
CVE-2026-102268 affects PyJWT < 2.14.0, Python applications using PyJWT for JWT auth (mixing HMAC and asymmetric algs). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-102268?
Upgrade PyJWT to 2.14.0, rotate keys, revoke issued tokens
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
An attacker who knows the public key can forge HMAC-signed JWTs, enabling authentication bypass, impersonation, and privilege escalation.
Immediate action required
- affected< 2.14.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.