Skip to content

chore(deps): update dependency cryptography to v46 [security]#278

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/pypi-cryptography-vulnerability
Open

chore(deps): update dependency cryptography to v46 [security]#278
renovate[bot] wants to merge 1 commit intomainfrom
renovate/pypi-cryptography-vulnerability

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Feb 11, 2026

This PR contains the following updates:

Package Change Age Confidence
cryptography (changelog) ==44.0.3==46.0.6 age confidence

GitHub Vulnerability Alerts

CVE-2026-34073

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


Release Notes

pyca/cryptography (cryptography)

v46.0.6

Compare Source

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

v46.0.0

Compare Source

v45.0.7

Compare Source

v45.0.6

Compare Source

v45.0.5

Compare Source

v45.0.4

Compare Source

v45.0.3

Compare Source

v45.0.2

Compare Source

v45.0.1

Compare Source

v45.0.0

Compare Source


Configuration

📅 Schedule: Branch creation - "" in timezone US/Eastern, Automerge - At any time (no schedule defined).

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

Rebasing: Whenever PR is behind base branch, 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 force-pushed the renovate/pypi-cryptography-vulnerability branch from 7c9a72e to 34f9f56 Compare March 14, 2026 02:00
@renovate renovate bot force-pushed the renovate/pypi-cryptography-vulnerability branch from 34f9f56 to 664e2f7 Compare March 26, 2026 19:49
@renovate renovate bot changed the title chore(deps): update dependency cryptography to v46 [security] chore(deps): update dependency cryptography to v46 [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 02:47
@renovate renovate bot changed the title chore(deps): update dependency cryptography to v46 [security] - autoclosed chore(deps): update dependency cryptography to v46 [security] Mar 28, 2026
@renovate renovate bot reopened this Mar 28, 2026
@renovate renovate bot force-pushed the renovate/pypi-cryptography-vulnerability branch from 664e2f7 to 097cb1a Compare March 28, 2026 18:35
@renovate renovate bot force-pushed the renovate/pypi-cryptography-vulnerability branch from 097cb1a to 8532065 Compare March 28, 2026 18:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants