| 1 | | ### Changes between 4.0.0 and 4.0.1 [9 Jun 2026] |
| 2 | | |
| 3 | | * Fixed heap use-after-free in `PKCS7_verify()`. |
| 4 | | |
| 5 | | Severity: High |
| 6 | | |
| 7 | | Issue summary: A specially crafted PKCS#7 or S/MIME signed message could |
| 8 | | trigger a use-after-free during PKCS#7 signature verification. |
| 9 | | |
| 10 | | Impact summary: A use-after-free may result in process crashes, heap |
| 11 | | corruption, or, potentially, remote code execution. |
| 12 | | |
| 13 | | CVE-2026-45447 |
| 14 | | |
| 15 | | * Fixed CMS `AuthEnvelopedData` processing may accept forged messages. |
| 16 | | |
| 17 | | Severity: Moderate |
| 18 | | |
| 19 | | Issue Summary: Cryptographic Message Services (CMS) processing fails |
| 20 | | to perform sufficient input validation on the cipher and tag length fields |
| 21 | | of `AuthEnvelopedData` containers, leading to various potential compromises. |
| 22 | | |
| 23 | | Impact Summary: Attackers making use of these vulnerabilities may achieve |
| 24 | | key-equivalent functionality for a given CMS recipient and/or bypass |
| 25 | | integrity validation for a given message. |
| 26 | | |
| 27 | | CVE-2026-34182] |
| 28 | | |
| 29 | | * Fixed unbounded memory growth in the QUIC `PATH_CHALLENGE` handler. |
| 30 | | |
| 31 | | Severity: Moderate |
| 32 | | |
| 33 | | Issue summary: Remote peer may exhaust heap memory of the QUIC server |
| 34 | | or client by flooding it with packets containing `PATH_CHALLENGE` frames. |
| 35 | | |
| 36 | | Impact summary: A malicious remote peer can cause an unbounded memory |
| 37 | | allocation which can lead to an abnormal termination of the application |
| 38 | | acting as a QUIC client or server and a Denial of Service. |
| 39 | | |
| 40 | | CVE-2026-34183 |
| 41 | | |
| 42 | | * Fixed double-free when checking OCSP stapled response. |
| 43 | | |
| 44 | | Severity: Moderate |
| 45 | | |
| 46 | | Issue summary: A malicious server can exploit TLS OCSP stapling by delivering |
| 47 | | a crafted response through the `status_request` extension, triggering |
| 48 | | a double-free in the client's certificate verification path. |
| 49 | | |
| 50 | | Impact summary: Successful exploitation allows an attacker to corrupt heap |
| 51 | | memory via a double-free, potentially leading to a Denial of Service |
| 52 | | or possibly an attacker controlled code execution or other undefined |
| 53 | | behavior. |
| 54 | | |
| 55 | | CVE-2026-35188 |
| 56 | | |
| 57 | | * Fixed NULL pointer dereference in QUIC server initial packet handling. |
| 58 | | |
| 59 | | Severity: Moderate |
| 60 | | |
| 61 | | Issue summary: Receiving a QUIC initial packet with an invalid token |
| 62 | | may trigger a NULL pointer dereference in the OpenSSL QUIC server |
| 63 | | with address validation disabled. |
| 64 | | |
| 65 | | Impact summary: NULL pointer dereference typically causes abnormal |
| 66 | | termination of the affected QUIC server process and a Denial of Service. |
| 67 | | |
| 68 | | CVE-2026-42764 |
| 69 | | |
| 70 | | * Fixed AES-OCB IV ignored on `EVP_Cipher()` path. |
| 71 | | |
| 72 | | Severity: Moderate |
| 73 | | |
| 74 | | Issue summary: When an application drives an AES-OCB context through |
| 75 | | the public `EVP_Cipher()` one-shot interface, the application-supplied |
| 76 | | initialisation vector (IV) is silently discarded. |
| 77 | | |
| 78 | | Impact summary: Every message encrypted under the same key uses the same |
| 79 | | effective nonce regardless of the IV supplied by the caller, resulting |
| 80 | | in `(key, nonce)` reuse and loss of confidentiality. If the same code path |
| 81 | | is used to compute the authentication tag, the tag depends only |
| 82 | | on the `(key, IV)` pair and not on the plaintext or ciphertext, allowing |
| 83 | | universal forgery of arbitrary ciphertext from a single captured message. |
| 84 | | |
| 85 | | CVE-2026-45445 |
| 86 | | |
| 87 | | * Fixed possible heap buffer overflow in ASN.1 multibyte string conversion. |
| 88 | | |
| 89 | | Severity: Low |
| 90 | | |
| 91 | | Issue summary: A signed integer overflow when sizing the destination |
| 92 | | buffer for Unicode output in `ASN1_mbstring_ncopy()` can lead to a heap |
| 93 | | buffer overflow. |
| 94 | | |
| 95 | | Impact summary: A heap buffer overflow may lead to a crash or possibly |
| 96 | | attacker controlled code execution or other undefined behaviour. |
| 97 | | |
| 98 | | CVE-2026-7383 |
| 99 | | |
| 100 | | * Fixed out-of-bounds read in CMS password-based decryption. |
| 101 | | |
| 102 | | Severity: Low |
| 103 | | |
| 104 | | Issue summary: When CMS password-based decryption ([RFC 3211]/PWRI key |
| 105 | | unwrap) processes attacker-supplied CMS data, an attacker-chosen stream-mode |
| 106 | | KEK cipher can trigger a heap out-of-bounds read in `kek_unwrap_key()`. |
| 107 | | |
| 108 | | Impact summary: A heap buffer over-read may trigger a crash, which leads |
| 109 | | to Denial of Service for an application if the input buffer ends at a memory |
| 110 | | page boundary and the following page is unmapped. There is no information |
| 111 | | disclosure, as the over-read bytes are not revealed to the attacker. |
| 112 | | |
| 113 | | CVE-2026-9076] |
| 114 | | |
| 115 | | * Fixed heap buffer over-read in ASN.1 content parsing. |
| 116 | | |
| 117 | | Severity: Low |
| 118 | | |
| 119 | | Issue summary: Parsing a crafted DER-encoded ASN.1 structure with a primitive |
| 120 | | element whose content exceeds 2 gigabytes in length may cause a heap buffer |
| 121 | | over-read on 64-bit Unix and Unix-like platforms. |
| 122 | | |
| 123 | | Impact summary: The heap buffer over-read may crash the application (Denial |
| 124 | | of Service) or to load into the decoded ASN.1 object contents of memory |
| 125 | | beyond the end of the input buffer. More typically, such ASN.1 elements |
| 126 | | would instead be truncated. |
| 127 | | |
| 128 | | CVE-2026-34180 |
| 129 | | |
| 130 | | * Fixed PKCS#12 files with PBMAC1 are accepted with short HMAC keys. |
| 131 | | |
| 132 | | Severity: Low |
| 133 | | |
| 134 | | Issue Summary: The PKCS#12 file processing fails to perform sufficient input |
| 135 | | validation for files that use Password-Based Message Authentication Code 1 |
| 136 | | (PBMAC1) integrity mechanism allowing a certificate and private key forgery. |
| 137 | | |
| 138 | | Impact Summary: An attacker impersonating a user can cause a service reading |
| 139 | | PKCS#12 files to accept forged certificates and private keys with a 1 in 256 |
| 140 | | probability. |
| 141 | | |
| 142 | | CVE-2026-34181 |
| 143 | | |
| 144 | | * Fixed NULL dereference in certificate verification with OCSP Checking. |
| 145 | | |
| 146 | | Severity: Low |
| 147 | | |
| 148 | | Issue summary: When a partial-chain certificate verification is enabled |
| 149 | | together with OCSP response checking for the whole chain, a NULL dereference |
| 150 | | will happen if the verified chain does not have a self-signed trusted anchor, |
| 151 | | crashing the process. |
| 152 | | |
| 153 | | Impact summary: A NULL pointer dereference can trigger a crash which leads |
| 154 | | to a Denial of Service for an application. |
| 155 | | |
| 156 | | CVE-2026-42765 |
| 157 | | |
| 158 | | * Fixed possible NULL dereference in password-dased CMS decryption. |
| 159 | | |
| 160 | | Severity: Low |
| 161 | | |
| 162 | | Issue summary: A specially crafted password-encrypted CMS message |
| 163 | | could trigger a NULL pointer dereference during CMS decryption. |
| 164 | | |
| 165 | | Impact summary: This NULL pointer dereference could lead to an application |
| 166 | | crash and a Denial of Service. |
| 167 | | |
| 168 | | CVE-2026-42766 |
| 169 | | |
| 170 | | * Fixed NULL pointer dereference in CRMF `EncryptedValue` decryption. |
| 171 | | |
| 172 | | Severity: Low |
| 173 | | |
| 174 | | Issue summary: An attacker-controlled CMP (Certificate Management Protocol) |
| 175 | | server could trigger a NULL pointer dereference in a CMP client application. |
| 176 | | |
| 177 | | Impact summary: A NULL pointer dereference could cause a crash |
| 178 | | of the application and a Denial of Service. |
| 179 | | |
| 180 | | CVE-2026-42767 |
| 181 | | |
| 182 | | * Fixed multi-`RecipientInfo` Bleichenbacher Oracle in `CMS_decrypt()` |
| 183 | | and `PKCS7_decrypt()`. |
| 184 | | |
| 185 | | Severity: Low |
| 186 | | |
| 187 | | Issue summary: The `CMS_decrypt()` and `PKCS7_decrypt()` functions |
| 188 | | are vulnerable to Bleichenbacher-style attack when an attacker is able |
| 189 | | to provide CMS or S/MIME messages and observe the error code |
| 190 | | and/or decryption output. |
| 191 | | |
| 192 | | Impact summary: The Bleichenbacher-style attack allows an attacker to use |
| 193 | | the victim's vulnerable application as a way to decrypt or sign messages |
| 194 | | with the victim's private RSA key. |
| 195 | | |
| 196 | | CVE-2026-42768 |
| 197 | | |
| 198 | | * Fixed trust anchor substitution via `cert`/`issuer` typo in CMP |
| 199 | | `rootCaKeyUpdate`. |
| 200 | | |
| 201 | | Severity: Low |
| 202 | | |
| 203 | | Issue Summary: An error in the callback used to verify the certificate |
| 204 | | provided in a Root CA key update Certificate Management Protocol (CMP) |
| 205 | | message response rendered the certificate validation ineffectual, |
| 206 | | which could lead to escalation of credentials from the Registration |
| 207 | | Authority (RA) level to the root Certification Authority (root CA) level. |
| 208 | | |
| 209 | | Impact Summary: The Registration Authority could replace the root CA |
| 210 | | certificate for the CMP clients with an arbitrary root CA certificate. |
| 211 | | |
| 212 | | CVE-2026-42769 |
| 213 | | |
| 214 | | * Fixed FFC-DH peer validation uses attacker-supplied `q`. |
| 215 | | |
| 216 | | Severity: Low |
| 217 | | |
| 218 | | Issue summary: When `EVP_PKEY_derive_set_peer()` is called with a DHX (X9.42) |
| 219 | | peer key, the peer key is not properly checked for the subgroup membership. |
| 220 | | |
| 221 | | Impact summary: A malicious peer which presents an X9.42 key carrying |
| 222 | | the victim's `p` and `g` parameters, a forged `q = r` (a small prime factor |
| 223 | | of the cofactor `(p − 1)/q_local`), and a public value `Y` of order `r` can |
| 224 | | recover the victim's private key after a small number of key exchange |
| 225 | | attempts. |
| 226 | | |
| 227 | | CVE-2026-42770 |
| 228 | | |
| 229 | | * Fixed possible out of bounds read in `X509_VERIFY_PARAM_set1_email()`. |
| 230 | | |
| 231 | | Severity: Low |
| 232 | | |
| 233 | | Issue summary: When `X509_VERIFY_PARAM_set1_email()` is called |
| 234 | | by an application to validate a crafted e-mail address, such as during |
| 235 | | S/MIME message validation, an out of bounds read can happen. |
| 236 | | |
| 237 | | Impact summary: This out of bounds read will not directly exfiltrate |
| 238 | | the data read to the attacker, so, the most likely result is a crash |
| 239 | | and a Denial of Service. |
| 240 | | |
| 241 | | CVE-2026-42771 |
| 242 | | |
| 243 | | * Fixed incorrect tag processing for empty messages in AES-GCM-SIV |
| 244 | | and AES-SIV modes. |
| 245 | | |
| 246 | | Severity: Low |
| 247 | | |
| 248 | | Issue summary: The implementations of AES-SIV ([RFC 5297]) and AES-GCM-SIV |
| 249 | | ([RFC 8452]) mishandle the authentication of AAD (Additional Authenticated |
| 250 | | Data) with an empty ciphertext, allowing forgery of such messages. |
| 251 | | |
| 252 | | Impact summary: An attacker can forge empty messages with arbitrary AAD |
| 253 | | to the victim's application using these ciphers. |
| 254 | | |
| 255 | | [CVE-2026-45446] |
| 256 | | |
| 257 | | * Fixed a regression introduced in 4.0.0 that led to a `openssl pkey` |
| 258 | | command crash when it was invoked to encrypt a private key with password |
| 259 | | being provided interactively. |
| 260 | | |
| 261 | | * Fixed a regression introduced in 4.0.0 that led to `openssl s_client -adv` |
| 262 | | command prematurely terminating a session when reading input of 16384 bytes |
| 263 | | in one `read()` call. |
| 264 | | |
| 265 | | * Fixed TLS 1.3 server not sending `NewSessionTicket` message |
| 266 | | after ciphersuite mismatch. |
| 267 | | |
| 268 | | * Implemented validation of the minimal length of PSK identity |
| 269 | | being of at least one byte long, as required per [RFC 8446]. |
| 270 | | |
| 271 | | * Fixed usage of stale application buffer pointer by kTLS implementation |
| 272 | | after incomplete writes when `SSL_MODE_ACCEPT_MOVING_WRITE_BUFFER` is set, |
| 273 | | that led to invalid memory reads and sending of incorrect data. |
| | 1 | [entered in error] |
