chore(deps): bump pyjwt from 2.12.1 to 2.13.0 in /examples/example-ai-crewai

[dependabot]

Bumps pyjwt from 2.12.1 to 2.13.0.

Release notes

Sourced from pyjwt's releases.

2.13.0

PyJWT 2.13.0 — Security Release

This release bundles five security fixes plus three additional hardening / spec-compliance changes. We recommend all users upgrade.

Security

• GHSA-xgmm-8j9v-c9wx — JWK JSON accepted as HMAC secret (algorithm confusion). HMACAlgorithm.prepare_key previously rejected PEM- and SSH-formatted asymmetric keys but did not catch a JWK passed as a raw JSON string. In a verifier configured with both symmetric and asymmetric algorithms in algorithms=[…] and a raw-JSON JWK as the key, an attacker could forge HS256 tokens using the JWK text as the HMAC secret. The guard has been extended to reject any JWK-shaped JSON. Reported by @​aradona91.

• GHSA-jq35-7prp-9v3f — Algorithm allow-list bypass with PyJWK / PyJWKClient. When verifying with a PyJWK, the caller's algorithms=[…] allow-list was checked against the token header alg as a string only; actual verification used the algorithm bound to the PyJWK. An attacker who controlled a registered JWKS key could sign with one algorithm and advertise another on the header. PyJWT now requires the token header alg to match the PyJWK's algorithm before verification. Reported by @​sushi-gif.

• GHSA-w7vc-732c-9m39 — DoS via base64 decode of unused payload segment when b64=false. For detached-payload JWS (b64=false), the compact-form payload segment was base64-decoded before being discarded in favor of the caller-supplied detached_payload. An attacker could inflate the unused segment to force CPU + memory cost without holding a valid signature. The segment is now required to be empty per RFC 7515 Appendix F, and is no longer decoded. Reported by @​thesmartshadow.

• GHSA-993g-76c3-p5m4 — PyJWKClient accepts non-HTTP(S) URIs. PyJWKClient.fetch_data passed its URI to urllib.request.urlopen, which by default also handles file://, ftp://, and data: schemes. An application that fed an attacker-influenced URI into PyJWKClient could be coerced into reading local files or reaching other unintended schemes. PyJWKClient now rejects any URI whose scheme isn't http or https. Reported by @​KEIJOT.

• GHSA-fhv5-28vv-h8m8 — PyJWKClient cache wiped on fetch error. A finally-block put(jwk_set=None) cleared the JWK Set cache whenever a fetch raised, turning a transient JWKS-endpoint outage into application-wide auth failure. The cache write was moved into the success path; transient errors no longer evict valid cached keys. Reported by @​eddieran.

Fixed

• Reject empty HMAC keys outright in HMACAlgorithm.prepare_key with InvalidKeyError instead of accepting them with only a warning. Defends against the os.getenv("JWT_SECRET", "") footgun. Thanks to @​SnailSploit and @​spartan8806 for the reports.
• Forward per-call options (including enforce_minimum_key_length) from PyJWT.decode through to PyJWS._verify_signature. The option was previously silently dropped between the two layers, so it only took effect when set on the PyJWT instance. Thanks to @​WLUB for the report.
• RFC 7797 §3 compliance for b64=false: the encoder now auto-adds "b64" to crit, and the decoder rejects tokens that set b64=false without listing it in crit. Thanks to @​MachineLearning-Nerd for the report.

Changed

• Migrate the dev, docs, and tests package extras to dependency groups, by @​kurtmckee in #1152.

Upgrade notes

Most fixes are invisible to correctly-configured callers. A few behavioral changes you may encounter:

• Empty HMAC keys now raise. If your app passed "" or b"" as a secret (often via a missing env var, e.g. os.getenv("JWT_SECRET", "")), encode/decode will now raise InvalidKeyError. This is the intended behavior — fix the configuration.
• PyJWK decoding now requires the token's alg to match the JWK's algorithm. Previously a mismatch was silently honored if the header alg appeared in the allow-list. Tokens that relied on this mismatch will now fail with InvalidAlgorithmError.
• PyJWKClient now rejects non-HTTP(S) URIs at construction time. Tests or dev environments that fetched JWKS from file:// URIs need to switch to a local HTTP server or load the JWKS by other means (e.g. construct PyJWKSet.from_dict(...) directly).
• b64=false tokens are now strictly RFC 7515 / 7797 compliant. Tokens with a non-empty compact-form payload segment, or that omit "b64" from crit, will be rejected. PyJWT-produced tokens always satisfy both invariants, so round-trips through PyJWT are unaffected.
• enforce_minimum_key_length set per-call now takes effect. Callers who passed options={"enforce_minimum_key_length": True} to jwt.decode() previously got no enforcement; they will now get InvalidKeyError on undersized keys, as documented.

Full changelog: jpadilla/pyjwt@2.12.1...2.13.0

Changelog

Sourced from pyjwt's changelog.

v2.13.0 <https://github.com/jpadilla/pyjwt/compare/2.12.1...2.13.0>__

Security

- Reject JWK JSON documents passed as raw HMAC secrets in
  ``HMACAlgorithm.prepare_key`` to close an algorithm-confusion gap that
  the existing PEM/SSH guard did not cover. Reported by @aradona91 in
  `GHSA-xgmm-8j9v-c9wx <https://github.com/jpadilla/pyjwt/security/advisories/GHSA-xgmm-8j9v-c9wx>`__.
- Bind the JWT header ``alg`` to ``PyJWK.algorithm_name`` during
  verification so the caller's ``algorithms=[...]`` allow-list cannot be
  bypassed when decoding with a ``PyJWK`` / ``PyJWKClient`` key. Reported
  by @sushi-gif in `GHSA-jq35-7prp-9v3f <https://github.com/jpadilla/pyjwt/security/advisories/GHSA-jq35-7prp-9v3f>`__.
- Reject non-``http(s)`` URI schemes in ``PyJWKClient`` so attacker-
  influenced URIs cannot read local files or reach unintended schemes via
  urllib's default ``file://`` / ``ftp://`` / ``data:`` handlers. Reported
  by @KEIJOT in `GHSA-993g-76c3-p5m4 <https://github.com/jpadilla/pyjwt/security/advisories/GHSA-993g-76c3-p5m4>`__.
- Preserve the cached JWK Set on fetch errors in ``PyJWKClient.fetch_data``.
  The previous ``finally``-block ``put(None)`` pattern cleared the cache
  on any transient outage, turning one bad JWKS request into application-
  wide auth failure. Reported by @eddieran in `GHSA-fhv5-28vv-h8m8 <https://github.com/jpadilla/pyjwt/security/advisories/GHSA-fhv5-28vv-h8m8>`__.
- Skip the unconditional base64 decode of the compact-form payload segment
  when ``b64=false`` is set in the protected header, and require that
  segment to be empty (RFC 7515 Appendix F detached form). Closes an
  unauthenticated DoS amplifier. Reported by @thesmartshadow in
  `GHSA-w7vc-732c-9m39 <https://github.com/jpadilla/pyjwt/security/advisories/GHSA-w7vc-732c-9m39>`__.
Fixed

- Reject empty HMAC keys outright in ``HMACAlgorithm.prepare_key`` with
  ``InvalidKeyError`` instead of accepting them with only a warning.
  Thanks to @SnailSploit and @spartan8806 for independently flagging the
  footgun.
- Forward per-call ``options`` (including ``enforce_minimum_key_length``)
  from ``PyJWT.decode`` through to ``PyJWS._verify_signature`` so the
  option actually takes effect when set at the call site rather than only
  on the ``PyJWT`` instance. Thanks to @WLUB for the report.
- RFC 7797 §3 compliance for ``b64=false``: the encoder now auto-adds
  ``&quot;b64&quot;`` to the ``crit`` header parameter, and the decoder rejects
  tokens that set ``b64=false`` without listing it in ``crit``. Thanks to
  @MachineLearning-Nerd for the report.
Changed



Migrate the dev, docs, and tests package extras to dependency groups by @​kurtmckee in [#1152](https://github.com/jpadilla/pyjwt/issues/1152) &lt;https://github.com/jpadilla/pyjwt/pull/1152&gt;__

Commits

• 7144e45 Apply ruff format
• d2f4bec Restore cast() calls with cross-version type: ignore for prepare_key
• 22f478c Remove redundant casts in RSAAlgorithm.prepare_key and `ECAlgorithm.prepare...
• 95791b1 Bundle security fixes and hardening into 2.13.0
• dcc27a9 [pre-commit.ci] pre-commit autoupdate (#1155)
• 9d08a9a [pre-commit.ci] pre-commit autoupdate (#1146)
• b87c100 Bump codecov/codecov-action from 5 to 6 (#1154)
• 40e3147 Migrate development extras to dependency groups (#1152)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[github-actions]

posthog-python Compliance Report

Date: 2026-07-27 14:50:11 UTC
Duration: 338968ms

✅ All Tests Passed!

111/111 tests passed

---

Capture_V1 Tests

✅ 94/94 tests passed

View Details

Test	Status	Duration
Endpoint And Method.Targets V1 Endpoint	✅	519ms
Endpoint And Method.Does Not Use Legacy Endpoints	✅	1010ms
Required Headers.Has Authorization Bearer Header	✅	1010ms
Required Headers.Has Content Type Json	✅	1009ms
Required Headers.Has Posthog Sdk Info Format	✅	1010ms
Required Headers.Has Posthog Attempt Header	✅	1010ms
Required Headers.Has Posthog Request Id	✅	1011ms
Required Headers.Has Posthog Request Timestamp	✅	1009ms
Required Headers.Has User Agent	✅	1010ms
Body Format.Body Has Created At And Batch	✅	1009ms
Body Format.No Api Key In Body	✅	1010ms
Body Format.No Sent At In Body	✅	1010ms
Event Format.Event Has Required Root Fields	✅	1009ms
Event Format.Event Uuid Is Valid	✅	1010ms
Event Format.Event Timestamp Is Rfc3339	✅	1010ms
Event Format.Distinct Id Is String	✅	1009ms
Event Format.Distinct Id At Root Not Properties	✅	1010ms
Event Format.Custom Properties Preserved	✅	1010ms
Event Format.Set Properties Preserved	✅	1010ms
Event Format.Set Once Properties Preserved	✅	1009ms
Event Format.Groups Properties Preserved	✅	1010ms
Event Format.Sdk Generates Uuid If Not Provided	✅	1011ms
Event Format.Event Has Required Root Fields Batch	✅	1015ms
Event Format.Event Uuid Is Valid Batch	✅	1017ms
Event Format.Event Timestamp Is Rfc3339 Batch	✅	1015ms
Event Format.Distinct Id Is String Batch	✅	1014ms
Event Format.Distinct Id At Root Not Properties Batch	✅	1014ms
Event Format.Custom Properties Preserved Batch	✅	1014ms
Event Format.Set Properties Preserved Batch	✅	1016ms
Event Format.Set Once Properties Preserved Batch	✅	1017ms
Event Format.Groups Properties Preserved Batch	✅	1014ms
Event Format.Sdk Generates Uuid If Not Provided Batch	✅	1015ms
Batch Behavior.Multiple Events In Single Batch	✅	1507ms
Batch Behavior.Batch Envelope Smoke	✅	1017ms
Batch Behavior.Flush With No Events Sends Nothing	✅	1005ms
Batch Behavior.Flush At Triggers Batch	✅	1511ms
Batch Behavior.Created At Reflects Batch Creation Time	✅	1012ms
Deduplication.Generates Unique Uuids	✅	1507ms
Deduplication.Different Events Same Content Different Uuids	✅	1507ms
Deduplication.Preserves Uuid On Retry	✅	7516ms
Deduplication.Preserves Timestamp On Retry	✅	7509ms
Deduplication.Preserves Uuid And Timestamp On Batch Retry	✅	7517ms
Deduplication.No Duplicate Events In Batch	✅	1504ms
Header Behavior On Retry.Attempt Header Starts At One	✅	1010ms
Header Behavior On Retry.Attempt Header Increments On Retry	✅	14524ms
Header Behavior On Retry.Request Id Preserved On Retry	✅	7508ms
Header Behavior On Retry.Different Requests Have Different Request Ids	✅	3518ms
Header Behavior On Retry.Request Timestamp Changes On Retry	✅	7515ms
Response Format Validation.Success Response Has Uuid Keyed Results	✅	1007ms
Response Format Validation.Success Response Has Ok For Each Event	✅	1507ms
Response Format Validation.Success No Retry After When All Ok	✅	1507ms
Response Format Validation.Success Retry After Present When Retry Events	✅	2510ms
Response Format Validation.Success No Retry After When Drop Only	✅	1508ms
Response Format Validation.Response Echoes Request Id	✅	1011ms
Retry Behavior.Retries On 408	✅	7516ms
Retry Behavior.Retries On 500	✅	7512ms
Retry Behavior.Retries On 503	✅	9516ms
Retry Behavior.Retries On 504	✅	7512ms
Retry Behavior.Retryable Errors Have Retry After	✅	4508ms
Retry Behavior.Respects Retry After On Retryable Error	✅	12513ms
Retry Behavior.Does Not Retry On 400	✅	3510ms
Retry Behavior.Does Not Retry On 401	✅	3508ms
Retry Behavior.Does Not Retry On 402	✅	3508ms
Retry Behavior.Does Not Retry On 413	✅	3508ms
Retry Behavior.Does Not Retry On 415	✅	3506ms
Retry Behavior.Non Retryable Errors Have No Retry After	✅	3510ms
Retry Behavior.Implements Backoff	✅	23521ms
Retry Behavior.Max Retries Respected	✅	23532ms
Partial Batch Handling.Handles 200 Full Success	✅	3002ms
Partial Batch Handling.Handles 200 With All Ok	✅	4509ms
Partial Batch Handling.Does Not Retry Dropped Events	✅	4508ms
Partial Batch Handling.Does Not Retry Limited Events	✅	4509ms
Partial Batch Handling.Prunes Ok Events On Partial Retry	✅	7513ms
Partial Batch Handling.Prunes Dropped Events On Partial Retry	✅	7512ms
Partial Batch Handling.Retries Only Retry Events From Partial	✅	7508ms
Partial Batch Handling.Partial Retry Preserves Uuids	✅	7512ms
Partial Batch Handling.Partial Retry Attempt Header Increments	✅	7516ms
Partial Batch Handling.Partial Retry Request Id Preserved	✅	7507ms
Partial Batch Handling.Respects Retry After On Partial	✅	9515ms
Partial Batch Handling.Unknown Result Treated As Terminal	✅	4507ms
Partial Batch Handling.Mixed Ok Drop Limited No Retry	✅	4507ms
Compression.Sends Gzip Content Encoding	✅	1007ms
Compression.No Content Encoding When Disabled	✅	1008ms
Compression.Compressed Body Is Decompressible	✅	1009ms
Error Handling.Does Not Retry On Unknown 4Xx	✅	3509ms
Event Options.Cookieless Mode Override	✅	1007ms
Event Options.Disable Skew Correction Override	✅	1009ms
Event Options.Process Person Profile Override	✅	1008ms
Event Options.Product Tour Id Override	✅	1008ms
Event Options.Unset Options Omitted	✅	1008ms
Event Options.Options Override In Batch	✅	1012ms
Geoip And Historical Migration.Geoip Disable Injected Into Properties	✅	1009ms
Geoip And Historical Migration.Historical Migration Set In Body	✅	1008ms
Geoip And Historical Migration.Historical Migration Absent By Default	✅	1008ms

Feature_Flags Tests

✅ 17/17 tests passed

View Details

Test	Status	Duration
Request Payload.Request With Person Properties Device Id	✅	1007ms
Request Payload.Flags Request Uses V2 Query Param	✅	1007ms
Request Payload.Flags Request Hits Flags Path Not Decide	✅	1006ms
Request Payload.Flags Request Omits Authorization Header	✅	1007ms
Request Payload.Token In Flags Body Matches Init	✅	1006ms
Request Payload.Groups Round Trip	✅	1006ms
Request Payload.Groups Default To Empty Object	✅	1007ms
Request Payload.Disable Geoip False Propagates As Geoip Disable False	✅	1006ms
Request Payload.Disable Geoip Omitted Defaults To False	✅	1007ms
Request Payload.Flag Keys To Evaluate Contains Only Requested Key	✅	1006ms
Request Lifecycle.No Flags Request On Init Alone	✅	503ms
Request Lifecycle.No Flags Request On Normal Capture	✅	1506ms
Request Lifecycle.Two Flag Calls Produce Two Remote Requests	✅	1010ms
Request Lifecycle.Mock Response Value Is Returned To Caller	✅	1003ms
Retry Behavior.Retries Flags On 502	✅	1006ms
Retry Behavior.Retries Flags On 504	✅	1007ms
Side Effect Events.Get Feature Flag Captures Feature Flag Called Event	✅	1508ms

[turnipdabeets]

Auto-approved: Dependabot PR with passing CI.