openssl, branch openssl-3.0.20

Prepare for release of 3.0.20

2026-04-07T12:46:26Z

Reviewed-by: Neil Horman Reviewed-by: Eugene Syromiatnikov MergeDate: Tue Apr 7 12:46:28 2026 Release: yes

make update

2026-04-07T12:46:25Z

Reviewed-by: Neil Horman Reviewed-by: Eugene Syromiatnikov MergeDate: Tue Apr 7 12:46:26 2026 Release: yes

Copyright year updates

2026-04-07T12:44:48Z

Reviewed-by: Neil Horman Reviewed-by: Eugene Syromiatnikov MergeDate: Tue Apr 7 12:44:50 2026 Release: yes

CHANGES.md, NEWS.md: update for 3.0.20

2026-04-07T12:09:40Z

3.0.20 CHANGES.md includes the following: * CVE-2026-28387, CVE-2026-28388, CVE-2026-28389, CVE-2026-28390, CVE-2026-31789, CVE-2026-31790 * https://github.com/openssl/openssl/pull/30384 "Fix #19891 CONNECT request for IPv6 targets in OSSL_HTTP_proxy_connect" 3.0.20 NEWS.md includes the following: * CVE-2026-28387, CVE-2026-28388, CVE-2026-28389, CVE-2026-28390, CVE-2026-31789, CVE-2026-31790 Signed-off-by: Eugene Syromiatnikov Reviewed-by: Nikola Pajkovsky Reviewed-by: Matt Caswell Reviewed-by: Tomas Mraz MergeDate: Tue Apr 7 12:09:53 2026

CHANGES.md, NEWS.md: update the URL format for CVE URLs

2026-04-07T12:09:40Z

The URLs have been changed from [1] to [2]. [1] https://www.openssl.org/news/vulnerabilities.html [2] https://openssl-library.org/news/vulnerabilities/ Signed-off-by: Eugene Syromiatnikov Reviewed-by: Nikola Pajkovsky Reviewed-by: Matt Caswell Reviewed-by: Tomas Mraz MergeDate: Tue Apr 7 12:09:51 2026

CHANGES.md, NEWS.md: sort links in lexicographical order

2026-04-07T12:09:40Z

A specific order makes link addition more consistent moving forward. The links were sorted with "LC_ALL=C sort -V" command, "sort" is from GNU coreutils. Signed-off-by: Eugene Syromiatnikov Reviewed-by: Nikola Pajkovsky Reviewed-by: Matt Caswell Reviewed-by: Tomas Mraz MergeDate: Tue Apr 7 12:09:50 2026

80-test_cms.t: Accept success in malformed RSA decryption

2026-04-07T07:17:43Z

The decryption of the malformed encrypted message might succeed with some probability. We accept that as the testcase tries to trigger a crash which does not happen. Reviewed-by: Eugene Syromiatnikov Reviewed-by: Nikola Pajkovsky MergeDate: Tue Apr 7 07:16:44 2026 (cherry picked from commit 7b5ece69dee3fb78fcd2618df3bce5064a04c6dc)

rsa_kem: test RSA_public_encrypt() result in RSASVE

2026-04-06T19:52:42Z

RSA_public_encrypt() returns the number of bytes written on success and -1 on failure. Add regression coverage in evp_extra_test using invalid RSA pubkey which triggers -1 in RSA_public_encrypt() using encapsulation. Signed-off-by: Nikola Pajkovsky Reviewed-by: Saša Nedvědický Reviewed-by: Tomas Mraz MergeDate: Mon Apr 6 19:51:31 2026 (cherry picked from commit c61bbd3f873d28e098f503f0187459ed488977c9)

rsa_kem: validate RSA_public_encrypt() result in RSASVE

2026-04-06T19:52:41Z

RSA_public_encrypt() returns the number of bytes written on success and -1 on failure. With the existing `if (ret)` check, a provider-side RSA KEM encapsulation can incorrectly succeed when the underlying RSA public encrypt operation fails. In that case the code reports success, returns lengths as if encapsulation completed normally, and leaves the freshly generated secret available instead of discarding it. Tighten the success condition so RSASVE only succeeds when RSA_public_encrypt() returns a positive value equal to the modulus-sized output expected for RSA_NO_PADDING. Any other return value is treated as failure, and the generated secret is cleansed before returning. Fixes CVE-2026-31790 Signed-off-by: Nikola Pajkovsky Reviewed-by: Saša Nedvědický Reviewed-by: Tomas Mraz MergeDate: Mon Apr 6 19:51:30 2026 (cherry picked from commit 001e01db3e996e13ffc72386fe79d03a6683b5ac)

Avoid possible buffer overflow in buf2hex conversion

2026-04-06T19:41:18Z

Fixes CVE-2026-31789 Reviewed-by: Saša Nedvědický Reviewed-by: Tomas Mraz MergeDate: Mon Apr 6 19:41:24 2026