Bump cryptography from 49.0.0 to 50.0.0

[dependabot]

Bumps cryptography from 49.0.0 to 50.0.0.

Changelog

Sourced from cryptography's changelog.

50.0.0 - 2026-07-31

* **SECURITY ISSUE**:
  :func:`~cryptography.hazmat.primitives.serialization.pkcs7.pkcs7_decrypt_der`
  and its PEM and S/MIME variants no longer expose distinguishable errors or
  timing when unwrapping a ``RecipientInfo``'s ``encryptedKey``, which could
  act as a Bleichenbacher oracle for callers that decrypt untrusted messages.
  A random key is now substituted on failure, as described in :rfc:`3218`.
  Credit to **@X1AOxiang** for reporting the issue. **CVE-2026-69247**
* Deprecated Diffie-Hellman key exchange over finite fields (FFDH).
  Everything FFDH is deprecated, including the types in
  ``cryptography.hazmat.primitives.asymmetric.dh`` and loading FFDH keys or
  parameters with the key loading APIs. Users should migrate to a more
  modern key exchange algorithm.
* Added ``xof()`` class methods to
  :class:`~cryptography.hazmat.primitives.hashes.SHAKE128` and
  :class:`~cryptography.hazmat.primitives.hashes.SHAKE256` for constructing
  algorithm instances configured for use with
  :class:`~cryptography.hazmat.primitives.hashes.XOFHash`.
* The :mod:`X.509 verification <cryptography.x509.verification>` APIs are now
  considered stable and are subject to our API stability policy.
* Added the :doc:`/cobblestone` recipe, an implementation of the
  Cobblestone-128 and Cobblestone-256 instantiations of the `C2SP
  chunked-encryption specification
  <https://c2sp.org/chunked-encryption>`_ for streaming authenticated
  encryption of large messages.
* Parsing a Signed Certificate Timestamp list now rejects encodings that
  carry trailing bytes after the list or after an individual SCT, instead of
  silently ignoring them.
* Added support for using :class:`~cryptography.x509.Name` as a field type in
  the :doc:`/hazmat/asn1/index` module.
* Loading a public key or an EC private key now rejects DER where the
  ``subjectPublicKey`` (or EC ``publicKey``) ``BIT STRING`` declares a non-zero
  number of unused bits, instead of silently ignoring it.
* Parsing a CRL entry's ``InvalidityDate`` extension now rejects a
  ``GeneralizedTime`` that carries fractional seconds or another non-DER form,
  matching the strict encoding already required for every other X.509 time
  field.
* :func:`~cryptography.x509.ocsp.load_der_ocsp_request` and
  :func:`~cryptography.x509.ocsp.load_der_ocsp_response` now reject a request
  or response whose ``version`` field is not ``v1``, the only version defined
  by RFC 6960, matching the version validation already performed when loading
  certificates, CSRs and CRLs.
* :class:`~cryptography.hazmat.primitives.hashes.XOFHash` is now supported
  when building against AWS-LC.
* HMAC (and therefore PBKDF2-HMAC) with SHA-3 hashes is now supported when
  building against AWS-LC.
* Diffie-Hellman (:doc:`/hazmat/primitives/asymmetric/dh`) is now supported
  when building against AWS-LC.
</tr></table> 

... (truncated)

Commits

• dcb7050 Prepare for 50.0.0 release (#15372)
• 53fccd9 Don't leak how PKCS#7 encryptedKey decryption failed (#15369)
• d472f97 Add from __future__ import annotations to all src/ Python files (#15371)
• 908773d Bump downstream dependencies in CI (#15368)
• 2cc07cc Bump BoringSSL, OpenSSL, AWS-LC in CI (#15367)
• c94ede9 chore(deps): bump ruff from 0.16.0 to 0.16.1 (#15366)
• 67a8308 chore(deps): bump virtualenv from 21.7.0 to 21.7.1 (#15365)
• 95018ff Release the GIL in one-shot AEAD encrypt/decrypt (#15361)
• 6954733 Release the GIL during DH and DSA parameter generation (#15364)
• 6893b94 Import _serialization instead of serialization in x509/extensions (#15363)
• Additional commits viewable 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]

🤖 Claude Code Review

This is a straightforward Dependabot dependency bump (cryptography 49.0.0 → 50.0.0 in pyproject.toml), a dev/test-group pin used for building/signing artifacts, not runtime application code. Here's the review:

Code Quality

• ✅ Style conventions: Single-line version bump, consistent with the existing pinned-dependency format in pyproject.toml:39.
• ✅ No commented-out code.
• ✅ Meaningful names: N/A — dependency version only.
• ✅ DRY: N/A.
• ✅ Defects: No functional code changed. cryptography is in the development dependency group (pyproject.toml:29-48), not a runtime dependency of the package itself, so this bump does not affect the shipped library's behavior. No lockfile (e.g., uv.lock/poetry.lock) is present in the diff to verify the resolved transitive tree, but since only the version pin string changed, that's expected for this PR.
• ✅ CLAUDE.md considerations: .claude/CLAUDE.md is unchanged by this PR and contains no environment-specific instructions — nothing to flag here.

Testing

• N/A — no new functions/endpoints introduced; this is purely a dependency version bump. No test changes expected or needed.

Documentation

• ❌ CHANGELOG.md not updated: The current [1.0.0] - Unreleased section (CHANGELOG.md:8-9) doesn't mention dependency bumps. Given this repo's history (recent merged bumps like coverage, virtualenv, etc. per git log), it appears dependency bumps are routinely not logged in CHANGELOG.md — consistent with prior practice, so this is likely fine, but flagging per the checklist.
• ✅ Markdown/CommonMark: no .md files touched in this diff.
• ✅ No inline comments needed for a version bump.

Security

• ✅ No hardcoded credentials.
• ✅ cryptography 50.0.0: This is a security-relevant library — bumping forward is generally a positive (picks up upstream fixes/hardening). No indication of a downgrade or pinning to a vulnerable version.
• ✅ No sensitive data in logs — N/A, no logging code touched.
• ✅ No .lic license files present in this diff.

Summary

No blocking issues. This is a safe, minimal dependency-version bump in a dev dependency group with no functional or security concerns identified.

Automated code review analyzing defects and coding standards

[github-actions]

🤖 Claude Code Review

PR Review: Bump cryptography 49.0.0 → 50.0.0

This is a routine Dependabot dependency bump, one line in pyproject.toml. Confirmed against ~20 prior identical Dependabot PRs in this repo's history (coverage, mypy, virtualenv, pytest, etc.) — none of them touch CHANGELOG.md, docs, or tests, so this PR is consistent with established project convention.

Code Quality

• ✅ Standard formatting, single dependency-pin line changed, no logic touched.
• ✅ No commented-out code.
• ✅ N/A — no new variables/identifiers.
• ✅ N/A — no duplication introduced.
• ✅ No defects: this is a version-pin bump only (pyproject.toml:39), no code paths exercised or changed.
• ✅ .claude/CLAUDE.md reviewed — it's already generic (env setup, lint commands, code style, project structure) with nothing environment-specific to a particular developer machine.

Testing

• ✅ N/A — no new functions/endpoints added.
• ✅ N/A — no new endpoints.
• ✅ N/A — no new logic/edge cases introduced.
• ⚠️ Test coverage impact: none, since no source code changed. Existing CI (pylint, spellcheck) and dependency-install steps will validate the new cryptography version resolves and installs cleanly — worth confirming CI passes given this is a major version bump (49 → 50) of a security-sensitive library, which can carry breaking API changes.

Documentation

• ✅ README: not applicable.
• ✅ API docs: not applicable.
• ✅ Inline comments: not applicable, no complex logic added.
• ✅ CHANGELOG.md: consistent with repo convention — no prior dependency-bump PR updates it.
• ✅ No markdown files touched in this diff.

Security

• ✅ No hardcoded credentials.
• ✅ N/A — no input-handling code changed.
• ✅ N/A — no error-handling code changed.
• ✅ No log statements touched.
• ✅ No .lic files or AQAAAD-prefixed strings present in this diff.

Note: cryptography is a security-critical dependency and this is a major version bump (49→50). Worth a quick check of the pyca/cryptography changelog referenced in the commit body for breaking changes/deprecations affecting this codebase's usage, even though this file only appears in the development dependency group here.

Overall: ✅ Approve. No issues found; matches the repo's standard Dependabot bump pattern.

Automated code review analyzing defects and coding standards