Skip to content

Update dependency cryptography to v46.0.7 [SECURITY]#36

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

Update dependency cryptography to v46.0.7 [SECURITY]#36
renovate[bot] wants to merge 1 commit intomainfrom
renovate/pypi-cryptography-vulnerability

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented May 7, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
cryptography (changelog) ==46.0.5==46.0.7 age adoption passing confidence

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

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

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


Release Notes

pyca/cryptography (cryptography)

v46.0.7

Compare Source

v46.0.6

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • ""
  • 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 force-pushed the renovate/pypi-cryptography-vulnerability branch from 3908dd7 to fa6dbaf Compare August 11, 2025 23:32
@renovate renovate Bot force-pushed the renovate/pypi-cryptography-vulnerability branch from fa6dbaf to 5f46679 Compare October 25, 2025 07:29
@renovate renovate Bot force-pushed the renovate/pypi-cryptography-vulnerability branch from 5f46679 to b4f54b0 Compare November 16, 2025 19:46
@renovate renovate Bot force-pushed the renovate/pypi-cryptography-vulnerability branch from b4f54b0 to e0b08dd Compare December 4, 2025 07:46
@renovate renovate Bot force-pushed the renovate/pypi-cryptography-vulnerability branch from e0b08dd to 7d2cb6c Compare February 3, 2026 08:03
@renovate renovate Bot force-pushed the renovate/pypi-cryptography-vulnerability branch from 7d2cb6c to 6972f5b Compare February 13, 2026 23:41
@renovate renovate Bot changed the title Update dependency cryptography to v44 [SECURITY] Update dependency cryptography to v46 [SECURITY] Mar 5, 2026
@renovate renovate Bot force-pushed the renovate/pypi-cryptography-vulnerability branch from 6972f5b to 36854cd Compare March 5, 2026 15:55
@renovate renovate Bot force-pushed the renovate/pypi-cryptography-vulnerability branch from 36854cd to 5bd2f6e Compare March 13, 2026 14:47
@renovate renovate Bot changed the title Update dependency cryptography to v46 [SECURITY] Update dependency cryptography to v46.0.6 [SECURITY] Apr 6, 2026
@renovate renovate Bot force-pushed the renovate/pypi-cryptography-vulnerability branch from 5bd2f6e to 5480eb4 Compare April 6, 2026 20:12
@renovate renovate Bot changed the title Update dependency cryptography to v46.0.6 [SECURITY] Update dependency cryptography to v46.0.7 [SECURITY] Apr 15, 2026
@renovate renovate Bot force-pushed the renovate/pypi-cryptography-vulnerability branch from 5480eb4 to 16b0b1f Compare April 15, 2026 16:56
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