NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI
PyPI, #875 most downloaded on PyPI
Implementation of JOSE Web standards
Latest stable
1.6.1
Last release 2 months ago
15 Sep 2026
Ships unpredictably
gaps range from 8 days to 2.1 years
Nearly every release is documented
notes for 27 of 30 stable releases
2 versions withdrawn
withdrawn after publishing
11 years old
32 releases · first in 2015
Drag across the ruler to compare, or tap a release to open it.
This release fixes CVE-2026-92091, a low security issue that may result in a Denial of Service on malformed JWK keys
This release fixes CVE-2026-92091, a low security issue that may result in a Denial of Service on malformed JWK keys
Full Changelog: v1.6.0...v1.6.1
This release fixes CVE-2026-92091, a low security issue that may result in a Denial of Service on malformed JWK keys
Full Changelog: https://github.com/latchset/jwcrypto/compare/v1.6.0...v1.6.1
Your coding agent can read these notes before it upgrades. Set up the MCP server →
This release fixes CVE-2026-84185, a low security issue that affects only very specific and uncommon uses of the JWS interface using a JWKSet.
This release fixes CVE-2026-84185, a low security issue that affects only very specific and uncommon uses of the JWS interface using a JWKSet.
Full Changelog: v1.5.9...v1.6.0
Add ML-DSA post-quantum signature support (RFC 9964) by @rjeffman in #384
CVE-2026-80179
Full Changelog: v1.5.8...v1.5.9
CVE-2026-80179
Full Changelog: https://github.com/latchset/jwcrypto/compare/v1.5.8...v1.5.9
Fix list iteration in claim format validation by @simo5 in #375
Full Changelog: v1.5.7...v1.5.8
Full Changelog: https://github.com/latchset/jwcrypto/compare/v1.5.7...v1.5.8
JWE: allow general (non flattened) serialization syntax by @Thomas-Mollard in #351
Full Changelog: v1.5.6...v1.5.7
Full Changelog: https://github.com/latchset/jwcrypto/compare/v1.5.6...v1.5.7
Address potential DoS with high compression ratio by @simo5 in #349
Full Changelog: v1.5.5...v1.5.6
Full Changelog: https://github.com/latchset/jwcrypto/compare/v1.5.5...v1.5.6
Version 1.5.6 - Moderate Security release
Compare
This version fixes a pypi distribution problem introduced in 1.0 when pushing was automated. With 1.5.5 a binary wheel is now also made available on p
This version fixes a pypi distribution problem introduced in 1.0 when pushing was automated. With 1.5.5 a binary wheel is now also made available on pypi.
Full Changelog: https://github.com/latchset/jwcrypto/compare/v1.5.4...v1.5.5
This version fixes a pypi distribution problem introduced in 1.0 when pushing was automated.
With 1.5.5 a binary wheel is now also made available on pypi.
Full Changelog: v1.5.4...v1.5.5
One more release bump to address issues with typing_extensions minimum required version
One more release bump to address issues with typing_extensions minimum required version
Full Changelog: https://github.com/latchset/jwcrypto/compare/v1.5.3...v1.5.4
Bumping release due to inconsistency in python 3.6 support that affected pypi jwcrypto-1.5.3.tar.gz.sha512sum.txt jwcrypto-1.5.3.tar.gz
Bumping release due to inconsistency in python 3.6 support that affected pypi jwcrypto-1.5.3.tar.gz.sha512sum.txt jwcrypto-1.5.3.tar.gz
Full Changelog: https://github.com/latchset/jwcrypto/compare/v1.5.2...v1.5.3
replace deprecated package with typing_extensions by @david-homelend in #337
This is a minor maintenance release to improve interoperability with debuggers
Note: yanked from pypi due to 3.6 incompatibility, use 1.5.3
Full Changelog: v1.5.1...v1.5.2
This is a minor security release to fix a potential DoS for applications that allow the use of symmetric keys with pbkdf2.
This is a minor security release to fix a potential DoS for applications that allow the use of symmetric keys with pbkdf2.
Full Changelog: v1.5.0...v1.5.1
This is a minor security release to fix a potential DoS for applications that allow the use of symmetric keys with pbkdf2.
Full Changelog: https://github.com/latchset/jwcrypto/compare/v1.5.0...v1.5.1
Minor bugfixes and the addition of Brainpool curves. As mentioned in the commit: "The use of these algorithms is specified solely by the gematik GmbH
Version 1.5
Minor bugfixes and the addition of Brainpool curves. As mentioned in the commit: "The use of these algorithms is specified solely by the gematik GmbH – National Digital Health Agency - for use in german e-health applications"
This version also raises the minimum Cryptography version required to 3.4 and the minimum python version tested to 3.7
Full Changelog: https://github.com/latchset/jwcrypto/compare/v1.4.2...v1.5.0
Another minor release to fix a mistake in the compatibility heuristics which affects actual applications
Another minor release to fix a mistake in the compatibility heuristics which affects actual applications
Full Changelog: https://github.com/latchset/jwcrypto/compare/v1.4.1...v1.4.2
Another minor release to fix a mistake in the compatibility heuristics which affects actual applications
Full Changelog: v1.4.1...v1.4.2
This is a minor release focused on improving backwards compatibility with applications after the API breaking changes introduced in 1.4 This patch add…
This is a minor release focused on improving backwards compatibility with applications after the API breaking changes introduced in 1.4 This patch adds a bunch of heuristics to be able to safely autodetect a token type. It has been tested to solve the compatibility issues (ie old code works without modifications and fully securely) with at least one large application.
Full Changelog: https://github.com/latchset/jwcrypto/compare/v1.4.0...v1.4.1
This is a security release to address CVE-2022-3102.
This is a security release to address CVE-2022-3102.
The JWT code can auto-detect the type of token being provided, and this can lead the application to incorrect conclusions about the trustworthiness of the token. Quoting the private disclosure we received : "Under certain circumstances, it is possible to substitute a [..] signed JWS with a JWE that is encrypted with the public key that is normally used for signature validation." This substitution attack can occur only if the validating application also have access to the private key, normally used to sign the tokens, available during validation of the received JWT. The significance of this attacks depends on the use of the token, it may lead to authentication bypass or authorization bypass (respectively if claims are used to authenticate or authorize certain actions), because the attacker has full control of the data placed in the JWE and can inject any desired claim value.
Several mitigating factors exist that can protect applications from this issue:
Normally, signing and validation are done by different applications, so this scenario should be unlikely. However it is possible to have applications that both sign and validate tokens and do not separate JWKs in use, or do not set a JWK 'use' type.
Due to the mitigating factors, and the fact that specific operational constraints and conditions need to be in place to successfully exploit this issue to generate an authentication bypass, we rate this security issue as moderate. Other avenues may decide on a different rating based on use case, always verify what conditions apply to your use of the library to assess risk.
Many thanks to Tom Tervoort of Secura for finding and reporting this issue.
In order to address this security issue certain changes had to be made that may make this update incompatible with some existing applications. Namely, a new 'expect_type' argument has been added to JWT; this argument now defaults to 'JWS' if not explicitly set unless a non default set of algorithms that include exclusively non-signing algorithms is set. In that case the default is switched to 'JWE', this is done to be as much backwards compatible as possible with any hint we are provided.
If the token passed to JWT for validation is not of the 'expected' type, an exception will be raised on validation. Note that a token can be de-serialized w/o validation by not providing a key at the time of de-serialization. This operation will continue to work regardless of expected type. The expectation apply exclusively at validation time. This is intentional as it allows applications that were de-serializing and then checking the type of token to keep working or do so with minimal modifications.
For applications that need more time to update there is a 'born-deprecated' module level variable that can be set to restore the old behavior and disregard expectations. See the jwcrypto jwt module documentation under the variables section for more details about that. We strongly discourage the use of this workaround and invite application developers to refactor their code to be safe rather then apply an unsafe workaround.
Full Changelog: https://github.com/latchset/jwcrypto/compare/v1.3.1...v1.4.0
Handle a regression when the JWTMissing Key exception was removed when a key is not found in a JWKSet. This adds a new generic JWKeyNotFound exception
Handle a regression when the JWTMissing Key exception was removed when a key is not found in a JWKSet. This adds a new generic JWKeyNotFound exception now returned by JWS and JWE when a JWKSet is used and JWTMissingKey now subclasses this new exception. This way code can now simply trap JWkeyNotFound, while older code can still use JWTMissingKey. Also fix documentation generation.
Full Changelog: https://github.com/latchset/jwcrypto/compare/v1.3.0...v1.3.1
Source README.md in setup to be used for PyPI by @simo5 in https://github.com/latchset/jwcrypto/pull/276
Full Changelog: https://github.com/latchset/jwcrypto/compare/v1.2.0...v1.3.0
Some new features and some fixes
Some new features and some fixes
Full Changelog: https://github.com/latchset/jwcrypto/compare/v1.1.0...v1.2.0
Cutting 1.0 as we reached a very stable code base and API now.
Cutting 1.0 as we reached a very stable code base and API now.
Simo Sorce (11):
Fixes a couple of serious regressions spotted in 0.9
Fixes a couple of serious regressions spotted in 0.9
Changelog:
…support for py34 as it stopped working on F33 Deprecate RSA1_5 and remove from defaults Make PBES2 behave like all other algorithms Enforce protected…
Changelog:
Arumugam (1): Adding Power support(ppc64le) with ci and testing to the project for architecture independent
Hielke (1): Added six as a dependency to avoid import error
Simo Sorce (11): Post release bump to 0.9.dev1 Make sure an empty dict is a valid JWT payload Turn JWK into a dict-like object Go one step further and provide access as attrs Drop support for py34 as it stopped working on F33 Deprecate RSA1_5 and remove from defaults Make PBES2 behave like all other algorithms Enforce protected header in compact serilization Add Rust in travis so we can build cryptography Fix importing Public EC keys from PEM files Release 0.9
Simon Willison (1): Installation instructions + extra badges
inyong_lee (1): RFC 8812 - Add Default allowed algorithms
Braden Pellett (2): Fix some documentation typos Rename ambiguous variable
Changelog:
Braden Pellett (2): Fix some documentation typos Rename ambiguous variable
Simo Sorce (5): Post release bump to 0.8.dev1 Remove cap on sphinx version Fix okp key type import Add method to export Keys ans Sets as dictionaries Release 0.8
Swatantra Agrawal (1): Typo rectified
inyong_lee (1): Add secp256k1 curve
Nothing published for this version
Nothing published for this version
Nothing published for this version
Fix bytes/str comparison in JWE
compatibility with cryptography 2.0
Fixed nbf incorrect validation #71
A regression was introduced in 0.3.0 that caused issues in FreeIPA and Custodia projects. Also docs version and tox/travis configurations were improve
A regression was introduced in 0.3.0 that caused issues in FreeIPA and Custodia projects. Also docs version and tox/travis configurations were improved to test Python 3.4 and 3.5 Python 3.3 is not officially supported anymore
Some interfaces have also been deprecated, and marked as such in the documentation, they may be removed in a future release.
This version completes the support for all algorithms specified by the JOSE RFCs, as well as adds better interfaces to deal with JWKs and implements the JWK Thumbprint standard too.
Some interfaces have also been deprecated, and marked as such in the documentation, they may be removed in a future release.
Fixed a few issues with symmetric and EC keys generation. Added more tests and Travis CI integration.
Fixed a few issues with symmetric and EC keys generation. Added more tests and Travis CI integration.
Now that the JOSE working group has produced official RFC it is time for a new release that updates all references and fixes a few bugs recently disco
Now that the JOSE working group has produced official RFC it is time for a new release that updates all references and fixes a few bugs recently discovered while using the library
One column per quarter.