[Snyk] Security upgrade pyjwt from 2.1.0 to 2.12.0

[ryanmcmorrowsnyk]

Snyk has created this PR to fix 1 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

• requirements.txt

⚠️ Warning

inflect 6.0.5 has requirement pydantic<2,>=1.9.1, but you have pydantic 1.8.2.
graphql-relay 3.1.0 has requirement typing-extensions<4,>=3.7; python_version < "3.8", but you have typing-extensions 4.7.1.
google-api-core 1.34.1 has requirement protobuf!=3.20.0,!=3.20.1,!=4.21.0,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<4.0.0dev,>=3.19.5, but you have protobuf 4.24.4.

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.
• Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[ryanmcmorrowsnyk]

This upgrade for PyJWT spans several minor versions and introduces environment and behavioral changes that require verification.

Key Changes:

• Python 3.7 Support Dropped: Version 2.9.0 and later no longer support Python 3.7.
• Stricter Validation: Version 2.12.0 fixes a vulnerability (CVE-2026-32597) by correctly enforcing the crit (Critical) Header Parameter as required by RFC 7515. Previously, tokens with unrecognized values in the crit header were accepted; they will now be rejected. This change introduces stricter validation that could affect tokens from some issuers.

Recommendation:

• Verify that your production environment is running a supported Python version (3.8+).
• Test your JWT validation logic to ensure that existing tokens do not contain unrecognized crit header values that would cause them to be rejected by the new version.

Source: PyJWT Changelog

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.