Servers and applications
CVE-2024-9143
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…
- Severity
- High 8.8
- Published
- 16 Oct 2024
- Last changed
- 9 Nov 2026
- Added to UpHeron
- 9 Nov 2026
- Fixed in
- 1.0.2zl, 1.1.1zb, 3.0.16, 3.1.8, 3.2.4, 3.3.3
- Exploit chance
- 12% in the next 30 daysHigher than 96% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Read data · Change data · Take it down
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H- Sources
- NVD
Description
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 encoding of binary (GF(2^m)) curves that can't represent problematic input values. Thus the likelihood of existence of a vulnerable application is low.
In particular, the X9.62 encoding is used for ECC keys in X.509 certificates, so problematic inputs cannot occur in the context of processing X.509 certificates. Any problematic use-cases would have to be using an "exotic" curve encoding.
Affected software
| Software | Affected versions |
|---|---|
OpenSSLServers and applications · cpe:a:openssl:openssl |
|
About OpenSSL
open-source implementation of the SSL and TLS protocols
- GitHub stars
- 31,449GitHub, 15 Nov 2026
- Forks
- 11,615GitHub, 15 Nov 2026
- Latest release
- openssl-4.1.0GitHub, 15 Nov 2026
- Released
- 23 Oct 2026GitHub
- Developer
- Richard LevitteWikidata
- License
- Apache Software License 2.0Wikidata
- Written in
- C, assembly language, PerlWikidata
- First released
- 1998Wikidata
- First published on GitHub
- 15 Jan 2013GitHub
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 4.1 | 4.1.0 | Until 23 Nov 2027 |
| 4.0 | 4.0.3 | Until 14 May 2027 |
| 3.6 | 3.6.5 | Ended 1 Nov 2026 |
| 3.5 (LTS)LTS | 3.5.9 | Until 8 Apr 2030 |
| 3.4 | 3.4.8 | Ended 22 Oct 2026 |
| 3.3 | 3.3.7 | Ended 9 Apr 2026 |
From endoflife.date.
Vulnerabilities in OpenSSL
- In our list
- 335
- Published in the last 12 months
- 76
- Critical, last 12 months
- 6
- High, last 12 months
- 40
- Known exploited
- 1
- CVE-2026-95690Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory.Medium 5.3 18 Nov 2026
- CVE-2026-84786A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records.High 7.5 18 Nov 2026
- CVE-2026-121482Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size.High 7.5 18 Nov 2026
- CVE-2026-121481Calling EVP_EncodeBlock() with an input length close to INT_MAX may overflow the calculation of the encoded output size and write past the end of the caller-supplied output buffer.Critical 9.8 18 Nov 2026
- CVE-2026-107494The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames.Critical 9.1 18 Nov 2026
- CVE-2026-35190Out-of-Bounds Read in TLS 1.3 Key-Share Processing with Suite B Certificate FlagMedium 5.3 17 Nov 2026