Repository navigation
chore(deps): update dependency pyopenssl to v26 [security] - #756
Merged
Merged
Conversation
renovate
Bot
requested review from
cbartz,
javierdelapuente and
yhaliaw
as code owners
March 16, 2026 18:18
renovate
Bot
requested review from
florentianayuwono,
weiiwang01 and
yanksyoon
as code owners
March 16, 2026 18:18
renovate
Bot
force-pushed
the
renovate/pypi-pyopenssl-vulnerability
branch
from
March 17, 2026 06:47
2eadfc4 to
78071da
Compare
renovate
Bot
force-pushed
the
renovate/pypi-pyopenssl-vulnerability
branch
from
March 17, 2026 08:35
78071da to
e0f68ad
Compare
renovate
Bot
force-pushed
the
renovate/pypi-pyopenssl-vulnerability
branch
from
March 18, 2026 12:47
e0f68ad to
7c97afe
Compare
renovate
Bot
force-pushed
the
renovate/pypi-pyopenssl-vulnerability
branch
from
March 19, 2026 07:42
7c97afe to
2137e52
Compare
renovate
Bot
force-pushed
the
renovate/pypi-pyopenssl-vulnerability
branch
from
March 20, 2026 11:15
2137e52 to
30e1024
Compare
renovate
Bot
force-pushed
the
renovate/pypi-pyopenssl-vulnerability
branch
from
March 20, 2026 11:44
30e1024 to
89c6045
Compare
renovate
Bot
force-pushed
the
renovate/pypi-pyopenssl-vulnerability
branch
from
March 20, 2026 12:55
89c6045 to
f62e754
Compare
renovate
Bot
force-pushed
the
renovate/pypi-pyopenssl-vulnerability
branch
from
March 20, 2026 13:44
f62e754 to
8e7141c
Compare
renovate
Bot
force-pushed
the
renovate/pypi-pyopenssl-vulnerability
branch
from
March 20, 2026 20:19
8e7141c to
0a6e11f
Compare
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
==25.3.0→==26.0.0GitHub Vulnerability Alerts
CVE-2026-27448
If a user provided callback to
set_tlsext_servername_callbackraised an unhandled exception, this would result in a connection being accepted. If a user was relying on this callback for any security-sensitive behavior, this could allow bypassing it.Unhandled exceptions now result in rejecting the connection.
Credit to Leury Castillo for reporting this issue.
CVE-2026-27459
If a user provided callback to
set_cookie_generate_callbackreturned a cookie value greater than 256 bytes, pyOpenSSL would overflow an OpenSSL provided buffer.Cookie values that are too long are now rejected.
Release Notes
pyca/pyopenssl (pyOpenSSL)
v26.0.0Compare Source
Backward-incompatible changes:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
cryptographyversion is now 46.0.0.Deprecations:
^^^^^^^^^^^^^
Changes:
^^^^^^^^
DTLS1_COOKIE_LENGTHbytes. Previously this would result in a buffer-overflow. Credit to dark_haxor for reporting the issue. CVE-2026-27459OpenSSL.SSL.Connection.get_group_nameto determine which group name was negotiated.Context.set_tlsext_servername_callbacknow handles exceptions raised in the callback by callingsys.excepthookand returning a fatal TLS alert. Previously, exceptions were silently swallowed and the handshake would proceed as if the callback had succeeded. Credit to Leury Castillo for reporting this issue. CVE-2026-27448Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.