chore(deps): Bump cryptography from 48.0.1 to 50.0.0

[dependabot]

Bumps cryptography from 48.0.1 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.

[frahlg]

·@·d·ependabot r·ebase

(Updating this branch against main via the API produced a merge commit without a Signed-off-by trailer, which fails the dco check here. A Dependabot rebase should regenerate the branch cleanly.)

---

Generated by Claude Code

[frahlg]

Correction to my last comment: the Dependabot mention I posted didn't actually go through as a working command — this bot's own tooling appears to sanitize @-mentions in posted text (inserting characters), so it can't reliably invoke ·@·d·ependabot r·ebase through a comment.

Status as-is: the dco check is failing because my own update-branch call created merge commit dd1b77b, authored without a Signed-off-by trailer (the original Dependabot commit 5300f7b is correctly signed off). This needs a human to either:

• comment the literal text "at-dependabot rebase" (typed directly, not copy-pasted from here) to have Dependabot regenerate the branch cleanly, or
• merge main into this branch locally with git merge -s ours / a manual rebase and a git commit -s sign-off, then push.

The underlying change (cryptography 48.0.1 → 50.0.0, includes a security fix for CVE-2026-69247) is otherwise sound — no FFDH usage in this repo to worry about from the deprecation, and every other check passed before the branch update. Flagging for a maintainer to unstick.

---

Generated by Claude Code

[miravoss26]

Dependabot bump: cryptography 48.0.1 → 50.0.0 (two major versions), lockfile-only diff. drivers, packages, public-boundary, signed channel accepts this tree, and history-secret-scan all pass, so nothing in this repo's own surface broke against the new major.

• Blocking: dco check fails — dependabot's commit has no Signed-off-by: trailer. Routine dependabot behavior, not a code issue, but it'll block merge until either the DCO check has a bot exemption or someone re-pushes the commit with a sign-off.
• Worth a human glance: a 2-major-version jump on the crypto library is exactly the kind of dependency bump where "our tests pass" doesn't fully cover it — cryptography's major releases have dropped legacy algorithms/APIs before. Nothing in this diff touches usage sites (lockfile only), so low risk, but flagging since it's security-sensitive rather than routine.

No secrets, no new network destinations, no authz changes. Safe to merge from my read once the DCO gate is resolved.

[frahlg]

·@·d·ependabot r·ebase

---

Generated by Claude Code

[frahlg]

Automated maintenance pass: unstuck this one.

The dependabot-mention route is confirmed dead — posting the literal command still gets mangled in transit (see the comment right above this one), so ·@·d·ependabot r·ebase can't be triggered from here. Went with the manual path instead: reset the branch to the original signed-off dependabot commit (5300f7b), merged current main (now includes #76) into it cleanly with no conflicts, and amended the merge with git commit -s before force-pushing. dco, drivers, packages, public-boundary and history-secret-scan are all green on the new head (34226af); signed channel accepts this tree is still running as of this comment — will merge once it completes, no further conflicts expected since this only touches pyproject.toml/uv.lock.

Underlying change is still the CVE-2026-69247 fix (cryptography 48.0.1 → 50.0.0), no FFDH usage in this repo to worry about from the deprecation.

---

Generated by Claude Code

[miravoss26]

Dependabot bump: cryptography 48.0.1 → 50.0.0 (a two-major-version jump), pyproject.toml + uv.lock only, no source changes.

Findings:

• No secrets, no new transitive dependencies beyond the version bump, no injection surface — mechanical lock update.
• Two major versions is more than a routine patch: cryptography's release notes across 49→50 have historically dropped deprecated APIs and changed some default algorithm choices. Worth a quick check that nothing in this repo's driver code calls into an API that moved (I don't have visibility into actual usage from a lockfile diff alone).
• All 6 CI checks green (drivers, packages, dco, history-secret-scan, public-boundary, signed channel).

Not in the pr-steward merge allowlist (device-drivers isn't a listed repo) — review only, no merge either way. Looks safe to merge from my read given CI is green, but flagging the major-version jump for a human glance before merging given it's a crypto library.

[frahlg]

Current-main verification complete on fd17603. This repository uses cryptography only for Ed25519 signing and verification; there is no FFDH use. Local make check passed (3,524 passed, 1,421 skipped), and all six GitHub checks are green, including DCO, packages, drivers, and signed-channel validation.