OpenSSL third-party maintenance
OpenSSL 3.2
OpenSSL 3.2
The OpenSSL 3.2 reached end of service life on Nov 23, 2025. 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: Nov 23, 2025
Specifications
- product
- openssl
- release
- 3.2
- product Label
- OpenSSL
- release Label
- 3.2
- codename
- lts
- latest Version
- 3.2.6
- release Date
- 2023-11-23
- maintained
- source Url
- https://endoflife.date/openssl
Lifecycle Dates
- End of Service Life
- Nov 23, 2025
- Last OEM Support
- Nov 23, 2025
OpenSSL 3.2 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.2. 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.2?
Save 40-70%
Dramatically reduce your maintenance costs while maintaining the same level of support coverage.
Extend Asset Life
Continue using your OpenSSL 3.2 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.2 Support: Frequently Asked Questions
Is the OpenSSL 3.2 still supported?
OpenSSL ended support for the OpenSSL 3.2 on Nov 23, 2025. Third-party maintenance remains available and keeps the OpenSSL 3.2 supported with 24/7 engineering support and same-day replacement parts.
When is the OpenSSL 3.2 end of service life (EOSL) date?
OpenSSL lists the end of service life for the OpenSSL 3.2 as Nov 23, 2025.
Can I keep using the OpenSSL 3.2 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.2 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.2
15 published CVEs affect the OpenSSL 3.2, including 7 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-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-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-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-2024-6119 | HIGH | 7.5 | Sep 3, 2024 | Issue summary: Applications performing certificate name checks (e.g., TLS clients checking server certificates) may attempt to read an invalid memory address resulting in abnormal termination of the application process. Impact summary: Abnormal termination of an application can a cause a denial of service. Applications performing certificate name checks (e.g., TLS clients checking server certificates) may attempt to read an invalid memory address when comparing the expected name with an `other |
| CVE-2024-12797 | HIGH | 7.4 | Feb 11, 2025 | Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server may fail to notice that the server was not authenticated, because handshakes don't abort as expected when the SSL_VERIFY_PEER verification mode is set. Impact summary: TLS and DTLS connections using raw public keys may be vulnerable to man-in-middle attacks when server authentication failure is not detected by clients. RPKs are disabled by default in both TLS clients and TLS servers. The issue only arises whe |
| CVE-2023-6129 | MEDIUM | 6.5 | Jan 9, 2024 | Issue summary: The POLY1305 MAC (message authentication code) implementation contains a bug that might corrupt the internal state of applications running on PowerPC CPU based platforms if the CPU provides vector instructions. Impact summary: If 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 (message authentication code) implementation in OpenSSL for PowerPC CPUs res |
| CVE-2025-9232 | MEDIUM | 5.9 | Sep 30, 2025 | Issue summary: An application using the OpenSSL HTTP client API functions may trigger an out-of-bounds read if the 'no_proxy' environment variable is set and the host portion of the authority component of the HTTP URL is an IPv6 address. Impact summary: An out-of-bounds read can trigger a crash which leads to Denial of Service for an application. The OpenSSL HTTP client API functions can be used directly by applications but they are also used by the OCSP client functions and CMP (Certificate M |
| CVE-2025-9231 | MEDIUM | 5.9 | Sep 30, 2025 | Issue summary: A timing side-channel which could potentially allow remote recovery of the private key exists in the SM2 algorithm implementation on 64 bit ARM platforms. Impact summary: A timing side-channel in SM2 signature computations on 64 bit ARM platforms could allow recovering the private key by an attacker.. While remote key recovery over a network was not attempted by the reporter, timing measurements revealed a timing signal which may allow such an attack. OpenSSL does not directly |
| CVE-2023-6237 | MEDIUM | 5.9 | Apr 25, 2024 | Issue summary: Checking excessively long invalid RSA public keys may take a long time. Impact summary: Applications that use the function EVP_PKEY_public_check() to check RSA public keys may experience long delays. Where the key that is being checked has been obtained from an untrusted source this may lead to a Denial of Service. When function EVP_PKEY_public_check() is called on RSA public keys, a computation is done to confirm that the RSA modulus, n, is composite. For valid RSA keys, n is a |
| CVE-2024-2511 | MEDIUM | 5.9 | Apr 8, 2024 | Issue summary: Some non-default TLS server configurations can cause unbounded memory growth when processing TLSv1.3 sessions Impact summary: An attacker may exploit certain server configurations to trigger unbounded memory growth that would lead to a Denial of Service This problem can occur in TLSv1.3 if the non-default SSL_OP_NO_TICKET option is being used (but not if early_data support is also configured and the default anti-replay protection is in use). In this case, under certain condition |
| CVE-2024-0727 | MEDIUM | 5.5 | Jan 26, 2024 | Issue summary: Processing a maliciously formatted PKCS12 file may lead OpenSSL to crash leading to a potential Denial of Service attack Impact summary: Applications loading files in the PKCS12 format from untrusted sources might terminate abruptly. A file in PKCS12 format can contain certificates and keys and may come from an untrusted source. The PKCS12 specification allows certain fields to be NULL, but OpenSSL does not correctly check for this case. This can lead to a NULL pointer dereferen |
| CVE-2024-4603 | MEDIUM | 5.3 | May 16, 2024 | Issue summary: Checking excessively long DSA keys or parameters may be very slow. Impact summary: Applications that use the functions EVP_PKEY_param_check() or EVP_PKEY_public_check() to check a DSA public key or DSA parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service. The functions EVP_PKEY_param_check() or EVP_PKEY_public_check() perform various checks on DSA parameters. Som |
| CVE-2024-13176 | MEDIUM | 4.6 | Jan 20, 2025 | Issue summary: A timing side-channel which could potentially allow recovering the private key exists in the ECDSA signature computation. Impact summary: A timing side-channel in ECDSA signature computations could allow recovering the private key by an attacker. However, measuring the timing would require either local access to the signing application or a very fast network connection with low latency. There is a timing signal of around 300 nanoseconds when the top word of the inverted ECDSA no |
Related OpenSSL Products
All OpenSSL products →OpenSSL 3.2
Price in 24 hours · 40-70% below OEM