chore(deps): bump cryptography from 46.0.5 to 50.0.0 in /envs/carla_env

[dependabot]

Bumps cryptography from 46.0.5 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 bump of a security-critical library with behavioral and parsing changes; scope is limited to the Carla env lockfile with no application code edits.

Overview
Updates envs/carla_env/uv.lock only, pinning cryptography from 46.0.5 to 50.0.0 (new sdist/wheel hashes). That pulls in the 50.0.0 release, including the CVE-2026-69247 fix for PKCS#7 encryptedKey decryption oracles and tighter X.509/PKCS parsing in several code paths.

The lock refresh also drops platform markers on secretstorage’s cryptography and jeepney edges so those deps are listed unconditionally in the lock graph; runtime selection still comes from other packages (e.g. keyring on Linux).

^{Reviewed by Cursor Bugbot for commit e61a151. 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

Scope: Dependabot bump of cryptography 46.0.5 → 50.0.0. The diff touches one file (envs/carla_env/uv.lock) and zero Python source files.

Automated Checks

• Lint: PASS (not applicable to diff). No .py files are modified, so the usort / ruff format / ruff check pipeline has nothing in this diff to flag. (uv was not preinstalled in the review sandbox; I installed it and ran ruff directly to confirm. The repo-wide "would reformat" results are pre-existing / tool-version noise and unrelated to this lockfile change.)
• Debug code: CLEAN (not applicable to diff). check-debug.sh only scans src/, which this PR does not touch. Every print / TODO it reports is pre-existing docstring/CLI (rich.console) output — none introduced here.

Open RFCs Context

Active RFCs: 000, 001, 002, 003, 005 (In Review), 010 (Draft), 004 (no explicit status). None concern dependency management, lockfiles, or the cryptography / secretstorage packages, so none are implicated by this change.

Tier 1: Fixes Required

None. Lockfile-only change; all wheels/sdist carry pinned sha256 hashes from pypi.org, the package name is correct (no typosquat), and the lock resolves cleanly.

Tier 2: Alignment Discussion

Principle Conflicts

None identified. A transitive-dependency version bump does not touch the Gymnasium API (reset/step/state), reward-in-environment computation, client/server separation, the MCP↔WebSocket dual-API boundary, or agent-reset isolation.

RFC Conflicts

None identified.

Additional Observations (non-blocking)

1. cryptography is a deep transitive dependency — pulled in via authlib, joserfc, pyjwt[crypto], and secretstorage. It is not a direct dependency of carla_env (whose deps are openenv, fastapi, pydantic, uvicorn, requests), and no carla_env code imports it. Runtime blast radius is minimal.
2. Large major-version jump (46 → 50). cryptography major releases can drop older OpenSSL/platform support and remove deprecated APIs. Because it is transitive and unused directly here, functional risk is low, but it's worth letting the image-build / env-validation CI confirm the new wheels install on the target platform(s).
3. Incidental secretstorage marker change. The re-resolve also dropped the sys_platform != 'emscripten' and sys_platform != 'win32' markers from secretstorage's inner cryptography / jeepney deps. This is benign: secretstorage remains gated to sys_platform == 'linux' at the keyring level, so it and its deps still won't resolve on Windows/emscripten.

Summary

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

Routine, low-risk Dependabot lockfile bump — no code or alignment concerns. Recommend letting env build/validation CI confirm the new wheels install cleanly before merge.

  

_{Sent by Cursor Automation: Pre-review}

[cursor]

Alignment Review Report

Scope: Native Dependabot bump of cryptography 46.0.5 → 50.0.0. Diff = one file (envs/carla_env/uv.lock), zero Python source files.

Automated Checks

• Lint: PASS (not applicable to diff). No .py modified, so usort/ruff have nothing in this diff. (uv isn't preinstalled in the review sandbox; I installed it — the repo-wide ruff "would reformat" hits are pre-existing/tool-version noise, none in this diff.) uv lock --check --project envs/carla_env → PASS (123 pkgs resolved).
• Debug code: CLEAN (not applicable). check-debug.sh scans src/ only; this PR touches no src/.

Lockfile Verification (dependabot lock bump)

• Transitive, not direct. cryptography is a deep transitive dep (via authlib, joserfc, pyjwt[crypto], secretstorage); it is not a declared dep of carla_env, and no carla_env code imports it → minimal runtime blast radius.
• Hash integrity: all 46/46 locked 50.0.0 artifacts (1 sdist + 45 wheels) match PyPI's published sha256 exactly; none yanked.
• Constraint OK: 50.0.0 requires_python !=3.9.0,!=3.9.1,>=3.9 is satisfied by carla_env >=3.11; its only runtime dep (cffi) is already locked.
• Born-clean lock: revision = 3 already (not in diff); 0 HF-mirror refs at base and head (126 pypi.org/simple) → no index-source flip and no revision-bump side effect; no requires-dist re-sync. The diff contains only cryptography artifacts + one benign secretstorage marker line.

Security (positive signal)

The old 46.0.5 carries 11 advisories; 50.0.0 clears all of them, including CVE-2026-69247 / GHSA-g6cj-pr64-35w5, whose fixed_in is exactly 50.0.0 (others were fixed in 46.0.6 / 46.0.7 / 48.0.1 / 49.0.0). 50.0.0 itself has no known advisories. This is why the bump targets 50.0.0 specifically — the large 46→50 jump is justified, not a red flag.

Open RFCs Context

Active: 000, 001, 002, 003, 005 (In Review), 010 (Draft), 004 (no status header). None cover dependency management / PyPI / lockfiles → no RFC bearing on this change.

Tier 1: Fixes Required

None. Lock is internally consistent, artifacts are authentic, constraints satisfied.

Tier 2: Alignment Discussion

Principle Conflicts

None. A transitive dependency bump doesn't touch the Gymnasium API (reset/step/state), rewards-in-environment, client/server separation, or the MCP↔WebSocket dual-API boundary.

RFC Conflicts

None.

Process / repo-governance flag (recurring, non-blocking)

ALIGNMENT FLAG: native Dependabot uv PR modifies envs/** despite exclude-paths.

• Policy at stake: the dependency-update config in .github/dependabot.yml.
• The concern: the uv updater is configured directory: "/" + exclude-paths: ["envs/**"], yet this native dependabot/uv/envs/carla_env/… PR edits envs/carla_env/uv.lock. exclude-paths is a valid key, but the uv ecosystem isn't honoring it; the intended channel for env bumps is the aggregate codex/dependabot-envs-* roll-ups. Non-blocking (keeping envs patched — here with real CVE fixes — is desirable), but the config-vs-behavior mismatch is worth reconciling.
• Suggested reviewer: @burtenshaw (author of the exclude-paths config).

Additional Observations (non-blocking)

• Incidental secretstorage marker change. The re-resolve dropped the sys_platform != 'emscripten' and sys_platform != 'win32' markers from secretstorage's inner cryptography/jeepney deps. Benign: secretstorage stays gated to sys_platform == 'linux' at the keyring level, so it and its deps still won't resolve on Windows/emscripten.
• Routine: let the env image-build / validate-env-locks CI confirm the new wheels resolve on target platform(s).

Summary

• 0 mechanical (Tier 1) issues
• 1 alignment/process (Tier 2) point — the exclude-paths bypass (non-blocking, cc @burtenshaw)
• 0 RFC conflicts

Security-positive, born-clean transitive dependency bump. Hashes verified authentic against PyPI, lock consistent, constraints satisfied. The only standing note is the recurring Dependabot exclude-paths process mismatch.

  

_{Sent by Cursor Automation: Pre-review}

[cursor]

This is the substantive change (46.0.5 → 50.0.0). Verified against PyPI: all 46 locked artifacts (1 sdist + 45 wheels) match the published sha256 exactly and none are yanked; uv lock --check passes; requires_python (>=3.9, excluding 3.9.0/3.9.1) is satisfied by carla_env's >=3.11.

Security-positive: 46.0.5 carries 11 advisories, all cleared by 50.0.0 — including CVE-2026-69247 (GHSA-g6cj-pr64-35w5), whose fixed_in is exactly 50.0.0, which is why the bump lands on 50.0.0. cryptography is transitive here (via authlib/joserfc/pyjwt[crypto]/secretstorage), not imported by carla_env directly.

[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.