🛡️ openSUSE-SU-2026:20431-1 — python-pyjwt (CVE-2026-32597)

⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Security update for python-PyJWT

This update for python-PyJWT fixes the following issue:

Update to PyJWT 2.12.1:

  • CVE-2026-32597: PyJWT accepts unknown crit header extensions (bsc#1259616).

Changelog:

Update to 2.12.1:

  • Add missing typing_extensions dependency for Python < 3.11 in

#1150

Update to 2.12.0:

  • Annotate PyJWKSet.keys for pyright by @tamird in #1134
  • Close HTTPError response to prevent ResourceWarning on

Python 3.14 by @veeceey in #1133

  • Do not keep algorithms dict in PyJWK instances by @akx in

#1143

  • Use PyJWK algorithm when encoding without explicit

algorithm in #1148

  • Docs: Add PyJWKClient API reference and document the

two-tier caching system (JWK Set cache and signing key LRU

cache).

Update to 2.11.0:

  • Enforce ECDSA curve validation per RFC 7518 Section 3.4.
  • Fix build system warnings by @kurtmckee in #1105
  • Validate key against allowed types for Algorithm family in

#964

  • Add iterator for JWKSet in #1041
  • Validate iss claim is a string during encoding and decoding

by @pachewise in #1040

  • Improve typing/logic for options in decode, decode_complete

by @pachewise in #1045

  • Declare float supported type for lifespan and timeout by

@nikitagashkov in #1068

  • Fix SyntaxWarnings/DeprecationWarnings caused by invalid

escape sequences by @kurtmckee in #1103

  • Development: Build a shared wheel once to speed up test

suite setup times by @kurtmckee in #1114

  • Development: Test type annotations across all supported

Python versions, increase the strictness of the type

checking, and remove the mypy pre-commit hook by @kurtmckee

in #1112

  • Support Python 3.14, and test against PyPy 3.10 and 3.11 by

@kurtmckee in #1104

  • Development: Migrate to build to test package building in

CI by @kurtmckee in #1108

  • Development: Improve coverage config and eliminate unused

test suite code by @kurtmckee in #1115

  • Docs: Standardize CHANGELOG links to PRs by @kurtmckee in

#1110

  • Docs: Fix Read the Docs builds by @kurtmckee in #1111
  • Docs: Add example of using leeway with nbf by @djw8605 in

#1034

  • Docs: Refactored docs with autodoc; added PyJWS and

jwt.algorithms docs by @pachewise in #1045

  • Docs: Documentation improvements for "sub" and "jti" claims

by @cleder in #1088

  • Development: Add pyupgrade as a pre-commit hook by

@kurtmckee in #1109

  • Add minimum key length validation for HMAC and RSA keys

(CWE-326). Warns by default via InsecureKeyLengthWarning

when keys are below minimum recommended lengths per RFC

7518 Section 3.2 (HMAC) and NIST SP 800-131A (RSA). Pass

enforce_minimum_key_length=True in options to PyJWT or

PyJWS to raise InvalidKeyError instead.

  • Refactor PyJWT to own an internal PyJWS instance instead of

calling global api_jws functions.

Affected software

openSUSE-SU-2026:20431-1 is recorded against 1 package.

  • python-pyjwt (fixed in 2.12.1-160000.1.1)

Timeline and source

Published on 25 March 2026 and last revised on 3 April 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

bugzilla.suse.com (Report)
www.suse.com (Web)

Details

Severity Unknown
CVSS Score N/A
CVSS Vector N/A
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2026-03-25
Updated 2026-08-20
Modified 2026-04-03
Fix URL N/A

Affected Packages

Software From version Fixed in
python-pyjwt 2.12.1-160000.1.1

Free Vulnerability Check

Is your site affected by openSUSE-SU-2026:20431-1?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against openSUSE-SU-2026:20431-1 and other known CVE records.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesSUSESUSE 2026