CVE-2026-102273: PyJWT accepts public JWK containers as HMAC secrets

Published Sep 28, 2026
·
Updated

PyJWT is a Python implementation of JSON Web Token standards. From 2.13.0 until 2.14.0, PyJWT HMACAlgorithm.preparekey is affected because HMAC key guard only recognizes top-level public JWK forms and misses container representations. This occurs when an application allows HMAC and asymmetric algorithms and passes a public JWK container as the raw key. As a result, public asymmetric key material is accepted as the HMAC secret. Consequently, an attacker who knows the public key can forge a token with arbitrary authenticated claims. This issue is fixed in version 2.14.0.

Affected Software

1 affected component
pypi/pyjwt>=2.13.0<2.14.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade PyJWT to a version that resolves this vulnerability.

    Fixed in 2.14.0

Event History

Sep 28, 2026
CVE Published
via MITRE·08:38 PM
Data Sourced
via MITRE·08:38 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to token forgery?

Deployments are exposed when they use affected PyJWT versions, allow both HMAC and asymmetric algorithms, and pass a public JWK container as the raw key. In that configuration, anyone who knows the public key can forge tokens with arbitrary authenticated claims.

2

Does exploiting this require an existing account or user interaction?

No. The supplied vector indicates network access with no privileges and no user interaction required, although exploitation has high attack complexity because the vulnerable key and algorithm-handling configuration must be present.

3

What version resolves the issue?

Upgrade PyJWT to version 2.14.0. The affected range is from 2.13.0 until 2.14.0.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203