Skip to content

chore(deps): bump cryptography from 46.0.5 to 50.0.0 in /envs/sumo_rl_env - #1055

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/uv/envs/sumo_rl_env/cryptography-50.0.0
Closed

chore(deps): bump cryptography from 46.0.5 to 50.0.0 in /envs/sumo_rl_env#1055
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/uv/envs/sumo_rl_env/cryptography-50.0.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 4, 2026

Copy link
Copy Markdown
Contributor

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

Dependabot compatibility score

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-sensitive transitive crypto library (via Authlib/SecretStorage); low direct code impact but worth smoke-testing installs and any auth/keyring paths on target platforms.

Overview
Updates envs/sumo_rl_env/uv.lock so the resolved cryptography package moves from 46.0.5 to 50.0.0, including refreshed sdist/wheel URLs and hashes for the new release.

The lock refresh also simplifies a few transitive dependency markers (e.g. pandas and secretstorage entries) as part of re-resolution; there are no application or pyproject source changes in this PR.

Reviewed by Cursor Bugbot for commit 040cd1a. Bugbot is set up for automated code reviews on this repo. Configure here.

Bumps [cryptography](https://github.com/pyca/cryptography) from 46.0.5 to 50.0.0.
- [Changelog](https://github.com/pyca/cryptography/blob/main/CHANGELOG.rst)
- [Commits](pyca/cryptography@46.0.5...50.0.0)

---
updated-dependencies:
- dependency-name: cryptography
  dependency-version: 50.0.0
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
@bot-ci-comment

bot-ci-comment Bot commented Aug 4, 2026

Copy link
Copy Markdown

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 cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alignment Review Report

Automated two-tier review of the cryptography 46.0.5 → 50.0.0 transitive lock bump in envs/sumo_rl_env.

Automated Checks

  • Lint: PASS (for this PR). bash .claude/hooks/lint.sh exits 1, but only on the ~20 pre-existing unformatted envs/** files (agent_world_model_env, chat_env, opencode_env, …). sumo_rl_env is not among them (0 matches), and this PR touches only uv.lock, which is not linted. The meaningful check for a lock bump — uv lock --check --project envs/sumo_rl_envpasses (126 packages resolved).
  • Debug code: CLEAN. check-debug.sh scans src/ only; every hit is a pre-existing docstring print() / TODO. This PR touches only envs/sumo_rl_env/uv.lock.

Open RFCs Context

RFCs on main: 000–005 + 010 (In Review / Draft). None govern dependency management, PyPI indexes, or packaging, so a transitive security bump has no RFC surface. Runtime-API / rewards-in-env / client-server / MCP / credential invariants are likewise untouched.

Tier 1: Fixes Required

None. Verification of the bump:

  • Transitive → lock-only is correct. cryptography is not in pyproject.toml; it's pulled via authlib 1.6.12, pyjwt[crypto], and secretstorage 3.5.0 (the openenv → fastmcp → keyring chain). No pyproject / requires-dist edit is expected, and none is present.
  • Hashes verified against PyPI. sdist sha256:eeac2acb…a6c9 (880201 B) plus spot-checked wheels (cp311 / cp39 / pp311 / cp314) match pypi.org/pypi/cryptography/50.0.0/json sha256 + size exactly; none yanked. requires_python !=3.9.0,!=3.9.1,>=3.9 is satisfied by the env's >=3.10.
  • Born-clean lock. revision = 3 and 0 HF-mirror refs at both base and head (143 pypi.org/simple on each side); no files.pythonhosted.org line changed outside cryptography-*. So none of the usual re-lock side effects (index-flip / revision bump / requires-dist re-sync) apply here.
  • Security-positive. The 46 → 50 jump clears the 11 advisories carried by 46.0.5 (GHSA-g6cj-pr64-35w5 / CVE-2026-69247 is fixed in exactly 50.0.0, plus 10 earlier fixes); PyPI lists 0 vulnerabilities for 50.0.0. This justifies the large version jump.
  • Incidental benign marker normalizations (not a regression): the re-resolve also simplified redundant environment markers on pandas 2.3.3 / 3.0.1 inner deps (numpy / python-dateutil / pytz / tzdata) and on secretstorage (cryptography / jeepney). These are semantically equivalent within each entry's resolution-markers scope — pandas / numpy resolved versions are unchanged, and keyring still gates secretstorage to sys_platform == 'linux'. uv lock --check passing confirms overall consistency.

Tier 2: Alignment Discussion

Principle Conflicts

None identified. A transitive security patch touches no principle/invariant surface (Gym API, rewards-in-environment, client-server separation, MCP boundary, credential handling).

RFC Conflicts

None identified.

ALIGNMENT FLAG (process, non-blocking): native dependabot PR bypasses exclude-paths

  • Policy at stake: .github/dependabot.yml — the uv updater declares directory: "/" with exclude-paths: ["envs/**"] (commit 5f499da, #566).
  • The concern: this native dependabot/uv/envs/sumo_rl_env/cryptography-50.0.0 PR edits envs/sumo_rl_env/uv.lock, exactly the path exclude-paths: ["envs/**"] is meant to exclude. exclude-paths is valid config, but the uv ecosystem isn't honoring it (platform limitation); the intended channel for env bumps is the codex/dependabot-envs-* aggregate roll-ups. The change itself is correct and worth landing — this is only a note that the env-scope exclusion isn't taking effect. No action needed on this PR.
  • Suggested reviewer: @burtenshaw (author of the exclude-paths lines / dependabot config)

Summary

  • 0 mechanical issues to fix
  • 1 alignment point for human review (dependabot exclude-paths process note, non-blocking)
  • 0 RFC conflicts

Net: a clean, born-clean, security-positive transitive bump — safe to merge on its own merits.

Open in Web View Automation 

Sent by Cursor Automation: Pre-review

Comment thread envs/sumo_rl_env/uv.lock
[[package]]
name = "cryptography"
version = "46.0.5"
version = "50.0.0"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cryptography 46.0.5 → 50.0.0 (transitive via authlib / pyjwt[crypto] / secretstorage).

Verified: sdist sha256:eeac2acb…a6c9 + spot-checked wheels (cp311/cp39/pp311/cp314) match PyPI exactly (none yanked); requires_python !=3.9.0,!=3.9.1,>=3.9 ⊇ env >=3.10; uv lock --check passes (126 pkgs).

Security-positive — clears the 11 advisories on 46.0.5 (incl. CVE-2026-69247, fixed in exactly 50.0.0); 0 vulns on 50.0.0.

Lock is born-clean (rev 3, all pypi.org/simple at base + head), so no index-flip / revision side effects.

@burtenshaw

Copy link
Copy Markdown
Collaborator

Closing in favor of aggregate env Dependabot PR #1015.

@burtenshaw burtenshaw closed this Aug 6, 2026
@dependabot @github

dependabot Bot commented on behalf of github Aug 6, 2026

Copy link
Copy Markdown
Contributor Author

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.

@dependabot
dependabot Bot deleted the dependabot/uv/envs/sumo_rl_env/cryptography-50.0.0 branch August 6, 2026 09:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

environment size: small Small pull request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant