OpenSSL third-party maintenance
OpenSSL 3.0 (LTS)
OpenSSL 3.0 (LTS)
The OpenSSL 3.0 (LTS) reached end of service life on Sep 7, 2026. Third-party maintenance keeps it supported — 24/7 engineering support and same-day replacement parts — at 40-70% below OEM renewal pricing. Coverage is available across North America, the United Kingdom and Europe, the Middle East, Asia-Pacific and Latin America, with next-business-day or 4-hour onsite response and no OEM software contract required.
- 24x7 support desk
- 4-hour onsite in major metros
- Spares held for every model we quote
- 5+ years past end of service life
- No OEM software contract required
- One contract for the whole rack
End of Service LifeEOSL Date: Sep 7, 2026
Specifications
- product
- openssl
- release
- 3.0
- product Label
- OpenSSL
- release Label
- 3.0 (LTS)
- codename
- lts
- true
- latest Version
- 3.0.22
- release Date
- 2021-09-07
- maintained
- true
- source Url
- https://endoflife.date/openssl
Lifecycle Dates
- End of Service Life
- Sep 7, 2026
- Last OEM Support
- Sep 7, 2026
OpenSSL 3.0 (LTS) Third-Party Maintenance Pricing
Choose the response level you need. We send an indicative price within 24 hours and a firm quote within 48, typically 40-70% below the OEM renewal.
Next business day
Price in 24 hours
Parts and engineer onsite next business day; 24x7 phone support.
Quote this level4-hour onsite
Price in 24 hours
4-hour onsite response in major metros, business hours.
Quote this level24x7, 4-hour onsite
Price in 24 hours
Mission-critical: 4-hour onsite response around the clock, 365 days.
Quote this levelCoverage across North America, the United Kingdom and Europe, the Middle East, Asia-Pacific and Latin America. Hardware maintenance does not require an active VMware, Broadcom or other OEM software contract.
OEM vs. 3rd Party Support
See how 3rd party maintenance compares to traditional OEM support for your OpenSSL 3.0 (LTS). Get the same level of service at a fraction of the cost.
| Feature | OEM Support | 3rd Party Support |
|---|---|---|
| Post-EOSL Support | ||
| 24/7/365 Support | ||
| Same-Day Parts Replacement | Limited | |
| Mixed-Vendor Support | ||
| Flexible Contract Terms | Annual Only | Month-to-Month Available |
| Asset Lifecycle Extension | ||
| OEM-Trained Engineers |
Why Choose 3rd Party Support for OpenSSL 3.0 (LTS)?
Save 40-70%
Dramatically reduce your maintenance costs while maintaining the same level of support coverage.
Extend Asset Life
Continue using your OpenSSL 3.0 (LTS) well beyond the OEM end-of-life date.
24/7 Expert Support
OEM-trained engineers available around the clock with same-day parts replacement.
OpenSSL 3.0 (LTS) Support: Frequently Asked Questions
Is the OpenSSL 3.0 (LTS) still supported?
OpenSSL ended support for the OpenSSL 3.0 (LTS) on Sep 7, 2026. Third-party maintenance remains available and keeps the OpenSSL 3.0 (LTS) supported with 24/7 engineering support and same-day replacement parts.
When is the OpenSSL 3.0 (LTS) end of service life (EOSL) date?
OpenSSL lists the end of service life for the OpenSSL 3.0 (LTS) as Sep 7, 2026.
Can I keep using the OpenSSL 3.0 (LTS) after its EOSL date?
Yes. EOSL means OpenSSL stops selling support contracts and issuing updates — the equipment itself keeps working. Third-party maintenance provides engineering support and replacement parts for as long as you choose to run it.
How much does third-party support for the OpenSSL 3.0 (LTS) cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location. You get an indicative price within 24 hours and a firm quote within 48.
Known Vulnerabilities Affecting OpenSSL 3.0 (LTS)
81 published CVEs affect the OpenSSL 3.0 (LTS), including 45 rated critical or high severity. OpenSSL no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2026-31789 | CRITICAL | 9.8 | Apr 7, 2026 | Issue summary: Converting an excessively large OCTET STRING value to a hexadecimal string leads to a heap buffer overflow on 32 bit platforms. Impact summary: A heap buffer overflow may lead to a crash or possibly an attacker controlled code execution or other undefined behavior. If an attacker can supply a crafted X.509 certificate with an excessively large OCTET STRING value in extensions such as the Subject Key Identifier (SKID) or Authority Key Identifier (AKID) which are being converted t |
| CVE-2025-9230 | CRITICAL | 9.8 | Sep 30, 2025 | Issue summary: An application trying to decrypt CMS messages encrypted using password based encryption can trigger an out-of-bounds read and write. Impact summary: This out-of-bounds read may trigger a crash which leads to Denial of Service for an application. The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service or Execution of attacker-supplied code. Although the consequences of a successful exploit of this vulnerability could |
| CVE-2024-4741 | CRITICAL | 9.8 | Nov 13, 2024 | Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause memory to be accessed that was previously freed in some situations Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, only applications that directly call the SSL_free_buffers function are affected by this issue. Applications that do not call this function are not vulnerable. Our investigations indicate that th |
| CVE-2022-2274 | CRITICAL | 9.8 | Jul 1, 2022 | The OpenSSL 3.0.4 release introduced a serious bug in the RSA implementation for X86_64 CPUs supporting the AVX512IFMA instructions. This issue makes the RSA implementation with 2048 bit private keys incorrect on such machines and memory corruption will happen during the computation. As a consequence of the memory corruption an attacker may be able to trigger a remote code execution on the machine performing the computation. SSL/TLS servers or other servers using 2048 bit RSA private keys runnin |
| CVE-2026-75803 | CRITICAL | 9.1 | Aug 25, 2026 | Issue summary: ChaCha20-Poly1305 and AES-OCB decryption with an empty ciphertext can report success without verifying the supplied authentication tag when the operation is finalized by calling the EVP_Cipher() function. Impact summary: Applications calling EVP_Cipher() on an empty ciphertext and expecting the call to check the AEAD tag may accept forged messages. CWE: CWE-354 (Improper Validation of Integrity Check Value) Description: The EVP_Cipher() API call for AEAD ciphers behaves like a |
| CVE-2026-34182 | CRITICAL | 9.1 | Jun 9, 2026 | Issue Summary: Cryptographic Message Services (CMS) processing fails to perform sufficient input validation on the cipher and tag length fields of AuthEnvelopedData containers, leading to various potential compromises. Impact Summary: Attackers making use of these vulnerabilities may achieve key-equivalent functionality for a given CMS recipient and/or bypass integrity validation for a given message. In one use case, an attacker may send a CMS message containing AuthEnvelopedData with the ciph |
| CVE-2024-5535 | CRITICAL | 9.1 | Jun 27, 2024 | Issue summary: Calling the OpenSSL API function SSL_select_next_proto with an empty supported client protocols buffer may cause a crash or memory contents to be sent to the peer. Impact summary: A buffer overread can have a range of potential consequences such as unexpected application beahviour or a crash. In particular this issue could result in up to 255 bytes of arbitrary private data from memory being sent to the peer leading to a loss of confidentiality. However, only applications that di |
| CVE-2026-45447 | HIGH | 8.8 | Jun 9, 2026 | Issue summary: A specially crafted PKCS#7 or S/MIME signed message could trigger a use-after-free during PKCS#7 signature verification. Impact summary: A use-after-free may result in process crashes, heap corruption, or potentially remote code execution. When processing a PKCS#7 or S/MIME signed message, if the SignedData digestAlgorithms field is present as an empty ASN.1 SET, OpenSSL may incorrectly free a caller-owned BIO during PKCS7_verify(). A subsequent use of the BIO by the calling app |
| CVE-2025-15467 | HIGH | 8.8 | Jan 27, 2026 | Issue summary: Parsing CMS AuthEnvelopedData or EnvelopedData message with maliciously crafted AEAD parameters can trigger a stack buffer overflow. Impact summary: A stack buffer overflow may lead to a crash, causing Denial of Service, or potentially remote code execution. When parsing CMS (Auth)EnvelopedData structures that use AEAD ciphers such as AES-GCM, the IV (Initialization Vector) encoded in the ASN.1 parameters is copied into a fixed-size stack buffer without verifying that its length |
| CVE-2024-9143 | HIGH | 8.8 | Oct 16, 2024 | Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the field polynomial can lead to out-of-bounds memory reads or writes. Impact summary: Out of bound memory writes can lead to an application crash or even a possibility of a remote code execution, however, in all the protocols involving Elliptic Curve Cryptography that we're aware of, either only "named curves" are supported, or, if explicit curve parameters are supported, they specify an X9.62 en |
| CVE-2026-84782 | HIGH | 8.2 | Sep 29, 2026 | Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly. Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region. CWE: |
| CVE-2026-7383 | HIGH | 8.1 | Jun 9, 2026 | Issue summary: A signed integer overflow when sizing the destination buffer for Unicode output in ASN1_mbstring_ncopy() can lead to a heap buffer overflow. Impact summary: A heap buffer overflow may lead to a crash or possibly attacker controlled code execution or other undefined behaviour. In ASN1_mbstring_copy() and ASN1_mbstring_ncopy() the destination size for Unicode output is computed in a signed int: by left shift of the input character count for BMPSTRING (UTF-16) and UNIVERSALSTRING ( |
| CVE-2026-28387 | HIGH | 8.1 | Apr 7, 2026 | Issue summary: An uncommon configuration of clients performing DANE TLSA-based server authentication, when paired with uncommon server DANE TLSA records, may result in a use-after-free and/or double-free on the client side. Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, the issue only affects clients that make use of TLSA records with both the PKIX-TA(0/PKIX-EE(1) certificate usa |
| CVE-2023-4807 | HIGH | 7.8 | Sep 8, 2023 | Issue summary: The POLY1305 MAC (message authentication code) implementation contains a bug that might corrupt the internal state of applications on the Windows 64 platform when running on newer X86_64 processors supporting the AVX512-IFMA instructions. Impact summary: If in an application that uses the OpenSSL library an attacker can influence whether the POLY1305 MAC algorithm is used, the application state might be corrupted with various application dependent consequences. The POLY1305 MAC |
| CVE-2026-63076 | HIGH | 7.5 | Aug 25, 2026 | Issue summary: OpenSSL CMP password based protection verification only checks whether the protectionAlg parameter was not NULL and not its ASN.1 type, before treating it as a PBMParameter. A crafted message can contain a parameter of a different type, which is then dereferenced as an invalid pointer. Impact summary: A remote, unauthenticated attacker can crash an application acting as a CMP server that accepts PBM-protected messages, or a CMP client talking to a malicious or intercepted CMP ser |
| CVE-2026-63072 | HIGH | 7.5 | Aug 25, 2026 | Issue summary: OpenSSL CMS decryption sizes the key-unwrap output buffer based on querying the unwrapped key size, but the AES-WRAP-PAD unwrap primitive can write and cleanse more bytes than that query reports, causing an 8-byte out-of-bounds heap write. Impact summary: An attacker who supplies a crafted CMS message can trigger a deterministic 8-byte out-of-bounds heap write when the victim decrypts it with CMS_decrypt(), corrupting the heap and typically resulting in a Denial of Service. CWE: |
| CVE-2026-54874 | HIGH | 7.5 | Aug 25, 2026 | Issue summary: Receiving a DTLS record for a future epoch while a handshake is in progress causes OpenSSL to buffer far more memory than the record itself requires. Impact summary: A peer can use a small amount of network traffic to make an OpenSSL DTLS endpoint retain a disproportionately large amount of memory, which may lead to a Denial of Service. CWE: CWE-405: Asymmetric Resource Consumption (Amplification) Description: While a DTLS handshake is in progress, a peer may legitimately have |
| CVE-2026-9076 | HIGH | 7.5 | Jun 9, 2026 | Issue summary: When CMS password-based decryption (RFC 3211 / PWRI key unwrap) processes attacker-supplied CMS data, an attacker-chosen stream-mode KEK cipher can trigger a heap out-of-bounds read in kek_unwrap_key(). Impact summary: A heap buffer over-read may trigger a crash which leads to Denial of Service for an application if the input buffer ends at a memory page boundary and the following page is unmapped. There is no information disclosure as the over-read bytes are not revealed to the |
| CVE-2026-45445 | HIGH | 7.5 | Jun 9, 2026 | Issue summary: When an application drives an AES-OCB context through the public EVP_Cipher() one-shot interface, the application-supplied initialisation vector (IV) is silently discarded. Impact summary: Every message encrypted under the same key uses the same effective nonce regardless of the IV supplied by the caller, resulting in (key, nonce) reuse and loss of confidentiality. If the same code path is used to compute the authentication tag, the tag depends only on the (key, IV) pair and not |
| CVE-2026-34180 | HIGH | 7.5 | Jun 9, 2026 | Issue summary: Parsing a crafted DER-encoded ASN.1 structure with a primitive element whose content exceeds 2 gigabytes in length may cause a heap buffer over-read on 64-bit Unix and Unix-like platforms. Impact summary: The heap buffer over-read may crash the application (Denial of Service) or to load into the decoded ASN.1 object contents of memory beyond the end of the input buffer. More typically such ASN.1 elements would instead be truncated. An integer truncation in OpenSSL's ASN.1 decod |
Showing the 20 most severe of 81 known CVEs.
Get Third Party SupportRelated OpenSSL Products
All OpenSSL products →OpenSSL 3.0 (LTS)
Price in 24 hours · 40-70% below OEM