You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Inquiry: ETA for v2.14.0 to address cryptography vulnerability (GHSA-537c-gmf6-5ccf)?
#1197
First, thank you for maintaining this excellent library!
Our team is currently blocked by a security vulnerability identified in the cryptography package: GHSA-537c-gmf6-5ccf.
To resolve this High-severity vulnerability, we must upgrade cryptography to >= 48.0.1. However, we noticed that current versions of PyJWT[crypto] (including 2.13.0) have upper-bound constraints that prevent us from upgrading to the patched cryptography versions.
We were wondering if there is any tentative timeline for a 2.14.0 release that updates the cryptography dependencies?
Alternatively, if there is an active PR or branch working on this compatibility update, we would be happy to track it. Any insight you could provide would really help us plan our security update strategy.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi PyJWT team,
First, thank you for maintaining this excellent library!
Our team is currently blocked by a security vulnerability identified in the cryptography package: GHSA-537c-gmf6-5ccf.
To resolve this High-severity vulnerability, we must upgrade cryptography to >= 48.0.1. However, we noticed that current versions of PyJWT[crypto] (including 2.13.0) have upper-bound constraints that prevent us from upgrading to the patched cryptography versions.
We were wondering if there is any tentative timeline for a 2.14.0 release that updates the cryptography dependencies?
Alternatively, if there is an active PR or branch working on this compatibility update, we would be happy to track it. Any insight you could provide would really help us plan our security update strategy.
Thanks again!
All reactions