Skip to content

Update dependency cryptography to v46.0.5 [SECURITY] - autoclosed#144

Closed
renovate[bot] wants to merge 1 commit into8/edgefrom
renovate/pypi-cryptography-vulnerability
Closed

Update dependency cryptography to v46.0.5 [SECURITY] - autoclosed#144
renovate[bot] wants to merge 1 commit into8/edgefrom
renovate/pypi-cryptography-vulnerability

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Dec 28, 2025

This PR contains the following updates:

Package Change Age Confidence
cryptography (changelog) 46.0.046.0.5 age confidence

GitHub Vulnerability Alerts

CVE-2026-26007

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

Release Notes

pyca/cryptography (cryptography)

v46.0.5

Compare Source

v46.0.4

Compare Source

v46.0.3

Compare Source

v46.0.2

Compare Source

v46.0.1

Compare Source


Configuration

📅 Schedule: Branch creation - "" in timezone Etc/UTC, 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 this update 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 renovate Bot added the not bug or enhancement PR is not 'bug' or 'enhancement'. For release notes label Dec 28, 2025
@renovate renovate Bot force-pushed the renovate/pypi-cryptography-vulnerability branch from a34a1b3 to d4e8a94 Compare December 29, 2025 02:06
@renovate renovate Bot changed the title Update dependency cryptography to v46 [SECURITY] Update dependency cryptography to v44 [SECURITY] Dec 29, 2025
@renovate renovate Bot force-pushed the renovate/pypi-cryptography-vulnerability branch 3 times, most recently from c528c78 to efa3696 Compare January 13, 2026 09:39
@renovate renovate Bot force-pushed the renovate/pypi-cryptography-vulnerability branch 2 times, most recently from 9bbe123 to 9f56770 Compare January 22, 2026 16:42
@renovate renovate Bot force-pushed the renovate/pypi-cryptography-vulnerability branch 2 times, most recently from 5346bed to dc6b4f1 Compare January 29, 2026 16:01
@renovate renovate Bot force-pushed the renovate/pypi-cryptography-vulnerability branch 3 times, most recently from 7ae005d to ac33ff2 Compare February 10, 2026 07:48
@renovate renovate Bot force-pushed the renovate/pypi-cryptography-vulnerability branch from ac33ff2 to f51eaa5 Compare February 11, 2026 03:10
@renovate renovate Bot changed the title Update dependency cryptography to v44 [SECURITY] Update dependency cryptography to v46 [SECURITY] Feb 11, 2026
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Feb 11, 2026

⚠️ 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: poetry.lock
Updating dependencies
Resolving dependencies...

Creating virtualenv non-package-mode-YIu8ppE6-py3.14 in /home/ubuntu/.cache/pypoetry/virtualenvs

Because no versions of pyopenssl match >24.2.1,<24.3.0 || >24.3.0,<25.0.0
 and pyopenssl (24.2.1) depends on cryptography (>=41.0.5,<44), pyopenssl (>=24.2.1,<24.3.0 || >24.3.0,<25.0.0) requires cryptography (>=41.0.5,<44).
And because pyopenssl (24.3.0) depends on cryptography (>=41.0.5,<45), pyopenssl (>=24.2.1,<25.0.0) requires cryptography (>=41.0.5,<45).
So, because non-package-mode depends on both pyOpenSSL (^24.2.1) and cryptography (^46.0.0), version solving failed.

@renovate renovate Bot force-pushed the renovate/pypi-cryptography-vulnerability branch from f51eaa5 to 39c8da5 Compare March 13, 2026 14:08
@renovate renovate Bot changed the title Update dependency cryptography to v46 [SECURITY] Update dependency cryptography to v46.0.5 [SECURITY] Mar 20, 2026
@renovate renovate Bot changed the title Update dependency cryptography to v46.0.5 [SECURITY] Update dependency cryptography to v46.0.5 [SECURITY] - autoclosed Mar 27, 2026
@renovate renovate Bot closed this Mar 27, 2026
@renovate renovate Bot deleted the renovate/pypi-cryptography-vulnerability branch March 27, 2026 01:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

not bug or enhancement PR is not 'bug' or 'enhancement'. For release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants