chore(deps): bump cryptography from 48.0.1 to 50.0.0 in /envs/websearch_env

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

---

Note

Medium Risk
Major cryptography upgrade includes a security fix (CVE-2026-69247) but touches crypto used by auth/JWT stacks (e.g. Authlib, PyJWT); lock-wide registry change could affect reproducibility if mirror contents differ.

Overview
Updates envs/websearch_env/uv.lock so the resolved cryptography package moves from 48.0.1 to 50.0.0, including refreshed wheel/sdist metadata for that release.

The lockfile also repoints every package source from the Hugging Face PyPI mirror to https://pypi.org/simple, bumps the lock revision to 3, and adjusts a few transitive dependency markers (e.g. pandas / secretstorage) to match the regenerated resolution graph.

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

chore(deps): bump cryptography 48.0.1 → 50.0.0 in /envs/websearch_env — native dependabot/uv/envs/websearch_env/cryptography-50.0.0, lock-only change to envs/websearch_env/uv.lock.

Automated Checks

• Lint: PASS (for this PR's scope). lint.sh exits 1 only on ~26 pre-existing unformatted .py files in other envs (agent_world_model/chat/coding_tools/jupyter/opencode/pi/repl/terminus/textarena); websearch_env appears 0 times and uv.lock is TOML (not linted).
• Debug code: CLEAN. check-debug.sh reports only pre-existing src/ CLI console.print/TODOs; this PR touches no src/.
• uv lock --check --project envs/websearch_env: PASS (124 packages).
• Hash integrity: PASS. All 46 cryptography-50.0.0 artifacts (1 sdist + 45 wheels) in the lock match PyPI sha256 + size + filename exactly; none yanked.
• Mergeability: clean 1-commit fast-forward on origin/main (git merge-tree → no conflict; base = current main tip 024eedc9).

Security (positive — effectively a security update)

Base 48.0.1 carries 3 distinct outstanding advisories, all cleared by ≤ 50.0.0:

• CVE-2026-69248 (GHSA-m2h6-j472-rp4c) → fixed 49.0.0
• CVE-2026-69249 (GHSA-jwv3-5hgf-82ww) → fixed 49.0.0
• CVE-2026-69247 (GHSA-g6cj-pr64-35w5) → fixed 50.0.0 only ⇒ justifies bumping to exactly 50.0.0

50.0.0 reports 0 known advisories. requires-python (!=3.9.0,!=3.9.1,>=3.9) is unchanged from 48.0.1 and satisfied by websearch_env's >=3.10. cryptography is a deep transitive dep (via authlib / joserfc / pyjwt[crypto] / secretstorage); no websearch_env code imports it → zero env-code blast radius.

Open RFCs Context

rfcs/ = 000–005 + 010 (all In Review except 010 Draft). None cover packaging / dependency management / PyPI index provenance ⇒ no RFC surface for this change.

Tier 1: Fixes Required

None. (Don't hand-edit a dependabot lockfile — registry/version choices are dependabot/team decisions.)

Tier 2: Alignment Discussion

Principle Conflicts

ALIGNMENT FLAG: declared-provenance flip on 129 packages (this lock was not "born clean")

• Principle at stake: "Container isolation for reproducibility" (PRINCIPLES.md L15) / "Performance for isolation" trade-off (L22)
• The concern: beyond the cryptography bump, the re-resolve rewrote every package source from the HF mirror https://pypi.registries.huggingface.tech/ to public https://pypi.org/simple (129 refs, 0 mirror left) and bumped revision = 2 → 3. Artifact URLs stay files.pythonhosted.org and all non-cryptography hashes are byte-identical ⇒ provenance-only / benign, but it changes the declared install index for the whole env. Flag, don't fix.
• Suggested reviewer: @Darktex (reproducibility principle, PRINCIPLES.md author) + @burtenshaw (dependabot config owner)

RFC Conflicts

None identified.

Process / FYI (non-blocking)

• exclude-paths bypass (cc @burtenshaw): .github/dependabot.yml sets the uv updater directory: "/" with exclude-paths: ["envs/**"], yet this native dependabot/uv/envs/websearch_env/... PR still edits envs/**. The uv ecosystem doesn't honor exclude-paths (dependabot-core#15102), and CVE-driven security updates can't be suppressed by it anyway (#14408) — so these env PRs appear despite the config. Intended path is the aggregated codex/dependabot-envs-* roll-up. No action on this PR.
• rev-3 / base-image uv heads-up (cc @burtenshaw): revision = 3 needs uv ≥ ~0.8. PR CI is fine (validate-env-locks uses uv 0.9.3). But websearch_env/server/Dockerfile only installs a fresh uv if ! command -v uv, and openenv-base ships uv 0.5.27 — a future image rebuild's uv sync --frozen could choke on rev 3. Latent only: docker-build.yml isn't triggered by uv.lock, and other rev-3 envs (openapp/jupyter) deploy fine.
• Benign churn: the diff also carries semantically-equivalent marker re-normalizations (pandas-family python-dateutil/pytz/tzdata and secretstorage's cryptography/jeepney markers simplified). No resolved version changed (only cryptography moved); uv lock --check confirms consistency, and secretstorage stays linux-gated via keyring.
• CI coverage FYI: websearch_env tests are --ignored in test.yml (network-dependent), so the bump gets no env-test coverage — but validate-env-locks still exercises the lock.

Summary

• 0 mechanical issues to fix
• 1 alignment point for human review (index/provenance flip — reproducibility, @darktex/@burtenshaw)
• 0 RFC conflicts
• Net security-positive (clears 3 distinct cryptography advisories; the 50.0.0-only fix for CVE-2026-69247 justifies the exact target)

  

_{Sent by Cursor Automation: Pre-review}

[cursor]

Security bump verified. cryptography 48.0.1 → 50.0.0. Base 48.0.1 had 3 distinct outstanding advisories — CVE-2026-69248 / CVE-2026-69249 (fixed 49.0.0) and CVE-2026-69247 fixed in 50.0.0 only (hence this exact target). 50.0.0 = 0 known advisories, not yanked, requires-python satisfied by websearch_env >=3.10. All 46 cryptography-50.0.0 artifacts match PyPI sha256 + size exactly. Transitive via authlib/joserfc/pyjwt[crypto]/secretstorage — no websearch_env code imports it.

[cursor]

Tier 2 — index-flip (reproducibility). This re-resolve flipped all 129 package source refs from the HF mirror (pypi.registries.huggingface.tech) to public pypi.org/simple (0 mirror left; this is the first flipped line — aiofile). Artifact URLs stay files.pythonhosted.org and non-cryptography hashes are unchanged ⇒ provenance-only / benign, but it changes the declared install index for the whole env. Flag for a maintainer decision (PRINCIPLES.md L15 reproducibility); please don't hand-revert here. cc @Darktex / @burtenshaw

[cursor]

Lock revision = 2 → 3 (side effect of the re-resolve). PR CI is fine — validate-env-locks runs uv 0.9.3. Heads-up only: server/Dockerfile installs a fresh uv only if ! command -v uv, and openenv-base ships uv 0.5.27 (too old for rev 3), so a future image rebuild's uv sync --frozen could fail. Latent: docker-build.yml isn't triggered by uv.lock, and other rev-3 envs already deploy fine. cc @burtenshaw

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