Update dependency cryptography to v48 [SECURITY]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
cryptography (changelog)	==46.0.7 → ==48.0.1
cryptography (changelog)	==45.0.5 → ==48.0.1

---

cryptography Vulnerable to a Subgroup Attack Due to Missing Subgroup Validation for SECT Curves

CVE-2026-26007 / GHSA-r6ph-v2qm-q3c2

More information

Details

Vulnerability Summary

The public_key_from_numbers (or EllipticCurvePublicNumbers.public_key()), EllipticCurvePublicNumbers.public_key(), load_der_public_key() and load_pem_public_key() functions do not verify that the point belongs to the expected prime-order subgroup of the curve.

This missing validation allows an attacker to provide a public key point P from a small-order subgroup. This can lead to security issues in various situations, such as the most commonly used signature verification (ECDSA) and shared key negotiation (ECDH). When the victim computes the shared secret as S = [victim_private_key]P via ECDH, this leaks information about victim_private_key mod (small_subgroup_order). For curves with cofactor > 1, this reveals the least significant bits of the private key. When these weak public keys are used in ECDSA , it's easy to forge signatures on the small subgroup.

Only SECT curves are impacted by this.

Credit

This vulnerability was discovered by:

• XlabAI Team of Tencent Xuanwu Lab
• Atuin Automated Vulnerability Discovery Engine

Severity

• CVSS Score: 8.2 / 10 (High)
• Vector String: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

References

• https://github.com/pyca/cryptography/security/advisories/GHSA-r6ph-v2qm-q3c2
• https://github.com/pyca/cryptography/commit/0eebb9dbb6343d9bc1d91e5a2482ed4e054a6d8c
• https://github.com/pyca/cryptography/releases/tag/46.0.5
• https://nvd.nist.gov/vuln/detail/CVE-2026-26007
• http://www.openwall.com/lists/oss-security/2026/02/10/4
• https://github.com/advisories/GHSA-r6ph-v2qm-q3c2

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

cryptography has incomplete DNS name constraint enforcement on peer names

CVE-2026-34073 / GHSA-m959-cc7f-wv43

More information

Details

Summary

In versions of cryptography prior to 46.0.5, DNS name constraints were only validated against SANs within child certificates, and not the "peer name" presented during each validation. Consequently, cryptography would allow a peer named bar.example.com to validate against a wildcard leaf certificate for *.example.com, even if the leaf's parent certificate (or upwards) contained an excluded subtree constraint for bar.example.com.

This behavior resulted from a gap between RFC 5280 (which defines Name Constraint semantics) and RFC 9525 (which defines service identity semantics): put together, neither states definitively whether Name Constraints should be applied to peer names. To close this gap, cryptography now conservatively rejects any validation where the peer name would be rejected by a name constraint if it were a SAN instead.

In practice, exploitation of this bypass requires an uncommon X.509 topology, one that the Web PKI avoids because it exhibits these kinds of problems. Consequently, we consider this a medium-to-low impact severity.

See CVE-2025-61727 for a similar bypass in Go's crypto/x509.

Remediation

Users should upgrade to 46.0.6 or newer.

Attribution

Reporter: @​1seal

Severity

• CVSS Score: 1.7 / 10 (Low)
• Vector String: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U

References

• https://github.com/pyca/cryptography/security/advisories/GHSA-m959-cc7f-wv43
• https://nvd.nist.gov/vuln/detail/CVE-2026-34073
• https://github.com/pypa/advisory-database/tree/main/vulns/cryptography/PYSEC-2026-35.yaml
• https://github.com/advisories/GHSA-m959-cc7f-wv43

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Cryptography vulnerable to buffer overflow if non-contiguous buffers were passed to APIs

CVE-2026-39892 / GHSA-p423-j2cm-9vmq

More information

Details

If a non-contiguous buffer was passed to APIs which accepted Python buffers (e.g. Hash.update()), this could lead to buffer overflows. For example:

h = Hash(SHA256())
b.update(buf[::-1])

would read past the end of the buffer on Python >3.11

Severity

• CVSS Score: 6.9 / 10 (Medium)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

References

• https://github.com/pyca/cryptography/security/advisories/GHSA-p423-j2cm-9vmq
• https://nvd.nist.gov/vuln/detail/CVE-2026-39892
• http://www.openwall.com/lists/oss-security/2026/04/08/12
• https://github.com/pypa/advisory-database/tree/main/vulns/cryptography/PYSEC-2026-36.yaml
• https://github.com/advisories/GHSA-p423-j2cm-9vmq

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Vulnerable OpenSSL included in cryptography wheels

GHSA-537c-gmf6-5ccf

More information

Details

pyca/cryptography's wheels include a statically linked copy of OpenSSL. The versions of OpenSSL included in wheels prior to cryptograph 48.01 are vulnerable to a security issue. More details about the vulnerability itself can be found in https://openssl-library.org/news/secadv/20260609.txt.

If you are building cryptography source ("sdist") then you are responsible for upgrading your copy of OpenSSL. Only users installing from wheels built by the cryptography project (i.e., those distributed on PyPI) need to update their cryptography versions.

Severity

• CVSS Score: 7.5 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

• https://github.com/pyca/cryptography/security/advisories/GHSA-537c-gmf6-5ccf
• https://openssl-library.org/news/secadv/20260609.txt
• https://github.com/advisories/GHSA-537c-gmf6-5ccf

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

pyca/cryptography (cryptography)

v48.0.1

Compare Source

v48.0.0

Compare Source

v47.0.0

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: fireblocks-plugin/uv.lock

Command failed: uv lock --upgrade-package cryptography
Using CPython 3.14.6 interpreter at: /opt/containerbase/tools/python/3.14.6/bin/python3
   Updating ssh://git@github.com/IBM/dapcs-oso-framework.git (master)
    Updated ssh://git@github.com/IBM/dapcs-oso-framework.git (ef8c44ebeec366251d1479378161c1c5bbc9e1ed)
  × No solution found when resolving dependencies:
  ╰─▶ Because only ibm-oso-framework==0.0.0 is available and
      ibm-oso-framework==0.0.0 depends on cryptography==45.0.5, we
      can conclude that all versions of ibm-oso-framework depend on
      cryptography==45.0.5.
      And because ibm-oso-fireblocks-plugin[dev] depends on ibm-oso-framework,
      we can conclude that ibm-oso-fireblocks-plugin[dev] depends on
      cryptography==45.0.5.
      And because your project depends on cryptography==48.0.1 and your
      project requires ibm-oso-fireblocks-plugin[dev], we can conclude that
      your project's requirements are unsatisfiable.