Bump PyJWT to 2.13.0 in /examples/cache_invalidation/web_service#1227
Merged
Conversation
mbouaziz
force-pushed
the
bump-pyjwt-blogger-cache_inv
branch
from
76b6f80 to
2f9fe94
Compare
…rvice Clears Dependabot alert #207 (GHSA-752w-5fwx-jx9f, PyJWT accepts unknown `crit` header extensions, patched in 2.12.0). The alert was created 2026-03-14 against PyJWT==2.8.0 and never auto-closed after PRs #1144 and #1145 bumped to 2.12.0; updating to 2.13.0 (latest) re-triggers Dependabot's scan and is itself a security release covering five additional CVEs (JWK-as-HMAC-secret, PyJWK alg bypass, base64 DoS, etc.) — none of which affect these apps' plain-string-secret + HS256 flow, but worth picking up. Bumping both web_service examples in lockstep since they were paired in the original PyJWT 2.8.0 -> 2.12.0 bump. Verified import + HS256 algorithm registration on Python 3.10 (system) and 3.12 (Dockerfile base) maps to the same code path. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
mbouaziz
force-pushed
the
bump-pyjwt-blogger-cache_inv
branch
from
2f9fe94 to
1bd85a3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Clears Dependabot alert #207 — GHSA-752w-5fwx-jx9f (PyJWT accepts unknown
critheader extensions, patched in 2.12.0).The alert was raised 2026-03-14 against
PyJWT==2.8.0. PR #1144 bumped to 2.12.0 (the first patched version) on 2026-05-20, but Dependabot never auto-closed the alert. Bumping to 2.13.0 (latest) forces a re-scan and is itself a security release: 5 additional CVEs fixed plus 3 hardening changes (JWK-as-HMAC-secret algorithm confusion, PyJWK/PyJWKClient algorithm allow-list bypass, base64 DoS, etc.).Compatibility
This app's PyJWT usage is the basic plain-string-secret + HS256 flow:
jwt.encode(token_data, JWT_SECRET, algorithm="HS256")jwt.decode(token, JWT_SECRET, algorithms=["HS256"])except jwt.ExpiredSignatureError/except jwt.InvalidTokenErrorNone of the 2.13.0 changes touch these APIs — the security fixes are around JWK/PyJWK paths we don't use.
Verified
import jwt; HS256 algorithm registeredcleanly with PyJWT 2.13.0 on Python 3.10 (system) — the Dockerfile uses Python 3.12.13 which exercises the same code path.🤖 Generated with Claude Code