chore(deps): bump cryptography from 47.0.0 to 50.0.0 in /envs/terminus_env

[dependabot]

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

---

Note

Medium Risk
Major-version cryptography upgrade affects TLS/crypto and PKCS#7 paths used by transitive deps; security fix is desirable but behavior changes (stricter parsing, PKCS#7 decrypt) warrant smoke tests of terminus_env auth flows.

Overview
Updates cryptography in envs/terminus_env/uv.lock from 47.0.0 to 50.0.0, refreshing pinned wheels/sdist hashes for that package. The bump is pulled in transitively (e.g. authlib, secretstorage); no application source files change.

50.0.0 includes a security fix (CVE-2026-69247) for PKCS#7 encryptedKey decryption that could leak oracle-style errors/timing, plus stricter X.509/OCSP parsing and deprecation of finite-field Diffie–Hellman. The diff also shows minor uv lock normalization (simpler environment markers on pandas and secretstorage entries), not separate dependency upgrades.

^{Reviewed by Cursor Bugbot for commit 58f92ca. Bugbot is set up for automated code reviews on this repo. Configure here.}

[bot-ci-comment]

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

[cursor]

Alignment Review Report

PR #1060 — chore(deps): bump cryptography from 47.0.0 to 50.0.0 in /envs/terminus_env (Dependabot)
Scope: 1 file changed — envs/terminus_env/uv.lock (+57 / −60). No Python or config source files touched.

Automated Checks

• Lint: Not applicable to this PR — no .py files changed. Running .claude/hooks/lint.sh against the full tree reports pre-existing formatting drift in ~26 envs/** Python files and README code fences (e.g. envs/echo_env/README.md), none of which are part of this PR. → No lint regression introduced by this change.
• Debug code: CLEAN for this PR. .claude/hooks/check-debug.sh flags only pre-existing console.print/print/TODO occurrences under src/openenv/cli/** — unrelated to this lock-file change. The lock file contains no debug artifacts.

Open RFCs Context

Current RFCs and statuses — none intersect dependency management or the cryptography library:

• RFC 000 Design Principles & Roadmap — In Review
• RFC 001 Abstractions — In Review
• RFC 002 Env Spec — In Review (+ proposed "Cloud Sandbox Providers" amendment pending author sign-off)
• RFC 003 MCP Support — In Review
• RFC 004 Rubrics — active (no explicit status header)
• RFC 005 Agentic Harnesses — In Review
• RFC 010 ECHO Env-token World Modeling — Draft

No RFC covers dependency pinning or terminus_env's transitive crypto stack → no RFC conflict.

Tier 1: Fixes Required

None. This is a Dependabot update to a generated uv.lock. It introduces no source code, imports, type/syntax changes, debug code, or credential exposure. Package sha256 hashes are pinned (good supply-chain hygiene), and bumping cryptography is a security-positive change.

Tier 2: Alignment Discussion

Principle Conflicts

None identified. A transitive-dependency lock bump does not touch the Gymnasium API, client/server separation, rewards-in-environment, agent isolation, or any decision in PRINCIPLES.md / INVARIANTS.md.

RFC Conflicts

None identified.

Notes / Observations (non-blocking, for the merger's awareness)

1. Major-version jump (47 → 50). Dependabot skips 48 and 49. cryptography is a transitive dep here (pulled via secretstorage; not listed in pyproject.toml and not imported by terminus_env code), and secretstorage accepts it unpinned in the lock — so direct breakage risk is low. Still worth confirming CI resolves/builds green, since cryptography majors can carry API/behavior changes for downstream consumers.
2. Wheel platform / Python-floor changes in 50.0.0.
   • Minimum CPython wheel moved cp38-abi3 → cp39-abi3 (Python ≥ 3.9). terminus_env requires >=3.10 → compatible.
   • macOS wheels changed from macosx_10_9_universal2 → macosx_11_0_arm64 only (no x86_64 macOS wheel). The env runs in a Linux container (manylinux/musllinux wheels present for x86_64/aarch64/ppc64le/armv7l) → runtime unaffected; only local dev on Intel macOS would fall back to an sdist build.
3. Incidental lock churn beyond cryptography. The diff also re-normalizes dependency markers for pandas (2.3.3, 3.0.2) and secretstorage (removing/simplifying now-redundant markers under resolution-markers). This is expected uv re-resolution behavior and is benign, but it explains why the diff is larger than a single-package bump.

Summary

• 0 mechanical issues to fix (Tier 1)
• 0 alignment points for human review (Tier 2)
• 0 RFC conflicts to discuss

Low-risk, security-positive Dependabot lock update with no alignment concerns. Recommend confirming CI (dependency resolution + terminus_env build) is green before merge.

  

_{Sent by Cursor Automation: Pre-review}

[burtenshaw]

Closing in favor of aggregate env Dependabot PR #1015.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.