CVE-2026-31789
published 2026-04-07CVE-2026-31789: 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…
PriorityP351critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EPSS
0.22%
13.2th percentile
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 to hex,
the size of the buffer needed for the result is calculated as multiplication
of the input length by 3. On 32 bit platforms, this multiplication may overflow
resulting in the allocation of a smaller buffer and a heap buffer overflow.
Applications and services that print or log contents of untrusted X.509
certificates are vulnerable to this issue. As the certificates would have
to have sizes of over 1 Gigabyte, printing or logging such certificates
is a fairly unlikely operation and only 32 bit platforms are affected,
this issue was assigned Low severity.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this
issue, as the affected code is outside the OpenSSL FIPS module boundary.
Affected
11 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | openssl | < openssl 3.0.19-1~deb12u2 (bookworm) | openssl 3.0.19-1~deb12u2 (bookworm) |
| msrc | azl3_openssl_3.3.5-4_on_azure_linux_3.0 | — | — |
| openssl | openssl | >= 0 < 3.5.6-r0 | 3.5.6-r0 |
| openssl | openssl | >= 0 < 3.5.6-r0 | 3.5.6-r0 |
| openssl | openssl | >= 0 < 3.0.19-1~deb12u2 | 3.0.19-1~deb12u2 |
| openssl | openssl | >= 0 < 3.5.5-1~deb13u2 | 3.5.5-1~deb13u2 |
| openssl | openssl | >= 3.0.0 < 3.0.20 | 3.0.20 |
| openssl | openssl | >= 3.3.0 < 3.3.7 | 3.3.7 |
| openssl | openssl | >= 3.4.0 < 3.4.5 | 3.4.5 |
| openssl | openssl | >= 3.5.0 < 3.5.6 | 3.5.6 |
| openssl | openssl | >= 3.6.0 < 3.6.2 | 3.6.2 |
CVSS provenance
nvdv3.19.8CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vendor_ubuntu7.5HIGH
vendor_redhat5.8LOW
vendor_msrc4.7MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Ubuntu
OpenSSL vulnerabilities
vendor_ubuntu·2026-04-09·CVSS 7.5
CVE-2026-28387 [HIGH] OpenSSL vulnerabilities
Title: OpenSSL vulnerabilities
Summary: Several security issues were fixed in OpenSSL.
USN-8155-1 fixed vulnerabilities in OpenSSL. This update provides the
corresponding updates for openssl and openssl1.0 packages for Ubuntu 14.04
LTS, Ubuntu 16.04 LTS, Ubuntu 18.04 LTS, and Ubuntu 20.04 LTS.
Original advisory details:
Viktor Dukhovni discovered that OpenSSL incorrectly negotiated the
expected preferred key exchange group when used as a TLS 1.3 server. This
could result in a less preferred key exchange being used, contrary to
expectations. This issue only affected Ubuntu 25.10. (CVE-2026-2673)
Igor Morgenstern discovered that OpenSSL incorrectly handled certain
memory operations when used as a DANE client. A remote attacker could use
this issue to cause OpenSSL to crash, resulting in
Ubuntu
OpenSSL vulnerabilities
vendor_ubuntu·2026-04-08·CVSS 7.5
CVE-2026-28388 [HIGH] OpenSSL vulnerabilities
Title: OpenSSL vulnerabilities
Summary: Several security issues were fixed in OpenSSL.
Viktor Dukhovni discovered that OpenSSL incorrectly negotiated the expected
preferred key exchange group when used as a TLS 1.3 server. This could
result in a less preferred key exchange being used, contrary to
expectations. This issue only affected Ubuntu 25.10. (CVE-2026-2673)
Igor Morgenstern discovered that OpenSSL incorrectly handled certain memory
operations when used as a DANE client. A remote attacker could use this
issue to cause OpenSSL to crash, resulting in a denial of service, or
possibly execute arbitrary code. (CVE-2026-28387)
Igor Morgenstern discovered that OpenSSL incorrectly handled certain memory
operations when processing a delta CRL. A remote attacker could possibly
use this iss
Red Hat
openssl: OpenSSL: Heap buffer overflow on 32-bit systems from large X.509 certificate processing
vendor_redhat·2026-04-07·CVSS 5.8
CVE-2026-31789 [LOW] CWE-190 openssl: OpenSSL: Heap buffer overflow on 32-bit systems from large X.509 certificate processing
openssl: OpenSSL: Heap buffer overflow on 32-bit systems from large X.509 certificate processing
A flaw was found in OpenSSL. This vulnerability, a heap buffer overflow, affects 32-bit systems when processing an unusually large X.509 certificate. If an application or service attempts to print or log such a specially crafted certificate, it could lead to a system crash or potentially allow an attacker to execute arbitrary code. This issue is considered low severity due to the specific conditions required for exploitation, including the need for an extremely large certificate and a 32-bit operating environment.
Statement: This issue has a Low impact. The vulnerability affects 32-bit systems and requires an application or service to process an unusually large X.509 certificate (over 1 Gigab
Microsoft
Heap Buffer Overflow in Hexadecimal Conversion
vendor_msrc·2026-04-02·CVSS 4.7
CVE-2026-31789 [MEDIUM] CWE-787 Heap Buffer Overflow in Hexadecimal Conversion
Heap Buffer Overflow in Hexadecimal Conversion
Mariner: Mariner
openssl: openssl
Customer Action Required: Yes
Debian
CVE-2026-31789: openssl - Issue summary: Converting an excessively large OCTET STRING value to a hexadecim...
vendor_debian·2026
CVE-2026-31789 CVE-2026-31789: openssl - Issue summary: Converting an excessively large OCTET STRING value to a hexadecim...
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 to hex, the size of the buffer needed for the result is calculated as multiplication of the input length by 3. On 32 bit platforms, this multiplication may overflow resulting in the allocation of a smaller buffer and a heap buffer overflow. Applications and services that print or log contents of untrus
GHSA
GHSA-j79m-9jxq-788r: Issue summary: Converting an excessively large OCTET STRING value to
a hexadecimal string leads to a heap buffer overflow on 32 bit platforms
ghsa_unreviewed·2026-04-08
CVE-2026-31789 CWE-787 GHSA-j79m-9jxq-788r: Issue summary: Converting an excessively large OCTET STRING value to
a hexadecimal string leads to a heap buffer overflow on 32 bit platforms
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 to hex,
the size of the buffer needed for the result is calculated as multiplication
of the input length by 3. On 32 bit platforms, this multiplication may overflow
resulting in the allocation of a smaller buffer and a heap buffer overflow.
Applications and services that print or log contents of unt
OSV
CVE-2026-31789: Issue summary: Converting an excessively large OCTET STRING value to
a hexadecimal string leads to a heap buffer overflow on 32 bit platforms
osv·2026-04-07
CVE-2026-31789 CVE-2026-31789: Issue summary: Converting an excessively large OCTET STRING value to
a hexadecimal string leads to a heap buffer overflow on 32 bit platforms
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 to hex,
the size of the buffer needed for the result is calculated as multiplication
of the input length by 3. On 32 bit platforms, this multiplication may overflow
resulting in the allocation of a smaller buffer and a heap buffer overflow.
Applications and services that print or log contents of unt
OSV
CVE-2026-31789: Issue summary: Converting an excessively large OCTET STRING value to a hexadecimal string leads to a heap buffer overflow on 32 bit platforms
osv·2026-04-07
CVE-2026-31789 CVE-2026-31789: Issue summary: Converting an excessively large OCTET STRING value to a hexadecimal string leads to a heap buffer overflow on 32 bit platforms
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 to hex, the size of the buffer needed for the result is calculated as multiplication of the input length by 3. On 32 bit platforms, this multiplication may overflow resulting in the allocation of a smaller buffer and a heap buffer overflow. Applications and services that print or log contents of untrus
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2026-31789 openssl: OpenSSL: Heap buffer overflow on 32-bit systems from large X.509 certificate processing
bugzilla·2026-03-25
CVE-2026-31789 [LOW] CVE-2026-31789 openssl: OpenSSL: Heap buffer overflow on 32-bit systems from large X.509 certificate processing
CVE-2026-31789 openssl: OpenSSL: Heap buffer overflow on 32-bit systems from large X.509 certificate processing
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 to hex,
the size of the buffer needed for the result is calculated as multiplication
of the input length by 3. On 32 bit platforms, this multiplication may overflow
resulting in the alloca
Wiz
CVE-2026-28388 Impact, Exploitability, and Mitigation Steps | Wiz
blogs_wiz·CVSS 7.5
CVE-2026-28388 [HIGH] CVE-2026-28388 Impact, Exploitability, and Mitigation Steps | Wiz
## CVE-2026-28388 :
OpenSSL vulnerability analysis and mitigation
Issue summary: When a delta CRL that contains a Delta CRL Indicator extension
is processed a NULL pointer dereference might happen if the required CRL
Number extension is missing.
Impact summary: A NULL pointer dereference can trigger a crash which
leads to a Denial of Service for an application.
When CRL processing and delta CRL processing is enabled during X.509
certificate verification, the delta CRL processing does not check
whether the CRL Number extension is NULL before dereferencing it.
When a malformed delta CRL file is being processed, this parameter
can be NULL, causing a NULL pointer dereference.
Exploiting this issue requires the X509_V_FLAG_USE_DELTAS flag to be enabled in
the verification context, the cert
Wiz
CVE-2026-28386 Impact, Exploitability, and Mitigation Steps | Wiz
blogs_wiz·CVSS 9.1
CVE-2026-28386 [CRITICAL] CVE-2026-28386 Impact, Exploitability, and Mitigation Steps | Wiz
## CVE-2026-28386 :
OpenSSL vulnerability analysis and mitigation
Issue summary: Applications using AES-CFB128 encryption or decryption on
systems with AVX-512 and VAES support can trigger an out-of-bounds read
of up to 15 bytes when processing partial cipher blocks.
Impact summary: This out-of-bounds 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 written to output.
The vulnerable code path is only reached when processing partial blocks
(when a previous call left an incomplete block and the current call provides
fewer bytes than needed to complete it). Additionally, the input buffer
must be positioned at a
Wiz
CVE-2026-28387 Impact, Exploitability, and Mitigation Steps | Wiz
blogs_wiz
CVE-2026-28387 CVE-2026-28387 Impact, Exploitability, and Mitigation Steps | Wiz
## CVE-2026-28387 :
OpenSSL vulnerability analysis and mitigation
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 usages and the DANE-TA(2) certificate
usage.
By far the most common deployment of DANE is in SMTP MTAs for which RFC7672
recommends that clients treat as 'unusable' any TLSA records that have the PKIX
certificate usages. These SMTP (o
Wiz
CVE-2026-28389 Impact, Exploitability, and Mitigation Steps | Wiz
blogs_wiz·CVSS 7.5
CVE-2026-28389 [HIGH] CVE-2026-28389 Impact, Exploitability, and Mitigation Steps | Wiz
## CVE-2026-28389 :
OpenSSL vulnerability analysis and mitigation
Issue summary: During processing of a crafted CMS EnvelopedData message
with KeyAgreeRecipientInfo a NULL pointer dereference can happen.
Impact summary: Applications that process attacker-controlled CMS data may
crash before authentication or cryptographic operations occur resulting in
Denial of Service.
When a CMS EnvelopedData message that uses KeyAgreeRecipientInfo is
processed, the optional parameters field of KeyEncryptionAlgorithmIdentifier
is examined without checking for its presence. This results in a NULL
pointer dereference if the field is missing.
Applications and services that call CMS_decrypt() on untrusted input
(e.g., S/MIME processing or CMS-based protocols) are vulnerable.
The FIPS modules in 3.6, 3.
Wiz
CVE-2026-28390 Impact, Exploitability, and Mitigation Steps | Wiz
blogs_wiz·CVSS 7.5
CVE-2026-28390 [HIGH] CVE-2026-28390 Impact, Exploitability, and Mitigation Steps | Wiz
## CVE-2026-28390 :
OpenSSL vulnerability analysis and mitigation
Issue summary: During processing of a crafted CMS EnvelopedData message
with KeyTransportRecipientInfo a NULL pointer dereference can happen.
Impact summary: Applications that process attacker-controlled CMS data may
crash before authentication or cryptographic operations occur resulting in
Denial of Service.
When a CMS EnvelopedData message that uses KeyTransportRecipientInfo with
RSA-OAEP encryption is processed, the optional parameters field of
RSA-OAEP SourceFunc algorithm identifier is examined without checking
for its presence. This results in a NULL pointer dereference if the field
is missing.
Applications and services that call CMS_decrypt() on untrusted input
(e.g., S/MIME processing or CMS-based protocols) are
Wiz
CVE-2026-31789 Impact, Exploitability, and Mitigation Steps | Wiz
blogs_wiz
CVE-2026-31789 CVE-2026-31789 Impact, Exploitability, and Mitigation Steps | Wiz
## CVE-2026-31789 :
OpenSSL vulnerability analysis and mitigation
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 to hex,
the size of the buffer needed for the result is calculated as multiplication
of the input length by 3. On 32 bit platforms, this multiplication may overflow
resulting in the allocation of a smaller buffer and a heap buffer ov
Wiz
CVE-2026-5190 Impact, Exploitability, and Mitigation Steps | Wiz
blogs_wiz·CVSS 7.5
CVE-2026-5190 [HIGH] CVE-2026-5190 Impact, Exploitability, and Mitigation Steps | Wiz
## CVE-2026-5190 :
Linux openSUSE vulnerability analysis and mitigation
Out-of-bounds write in the streaming decoder component in aws-c-event-stream before 0.6.0 might allow a third party operating a server to cause memory corruption leading to arbitrary code execution on a client application that processes crafted event-stream messages.
To remediate this issue, users should upgrade to version 0.6.0 or later.
Source : NVD
## 7.7
Score
Published March 31, 2026
Severity HIGH
CNA Score 7.7
Affected Technologies
Linux openSUSE
Has Public Exploit No
Has CISA KEV Exploit No
CISA KEV Release Date N/A
CISA KEV Due Date N/A
Exploitation Probability Percentile (EPSS) 5.4
Exploitation Probability (EPSS) N/A
Affected packages and libraries
aws-c-event-stream-devel
libaws-c-event-
Wiz
CVE-2026-31790 Impact, Exploitability, and Mitigation Steps | Wiz
blogs_wiz·CVSS 7.5
CVE-2026-31790 [HIGH] CVE-2026-31790 Impact, Exploitability, and Mitigation Steps | Wiz
## CVE-2026-31790 :
OpenSSL vulnerability analysis and mitigation
Issue summary: Applications using RSASVE key encapsulation to establish
a secret encryption key can send contents of an uninitialized memory buffer to
a malicious peer.
Impact summary: The uninitialized buffer might contain sensitive data from the
previous execution of the application process which leads to sensitive data
leakage to an attacker.
RSA_public_encrypt() returns the number of bytes written on success and -1
on error. The affected code tests only whether the return value is non-zero.
As a result, if RSA encryption fails, encapsulation can still return success to
the caller, set the output lengths, and leave the caller to use the contents of
the ciphertext buffer as if a valid KEM ciphertext had been produced.
https://github.com/openssl/openssl/commit/364f095b80601db632b0def6a33316967f863bdehttps://github.com/openssl/openssl/commit/7a9087efd769f362ad9c0e30c7baaa6bbfa65ecfhttps://github.com/openssl/openssl/commit/945b935ac66cc7f1a41f1b849c7c25adb5351f49https://github.com/openssl/openssl/commit/a24216018e1ede8ff01a4ff5afff7dfbd443e2f9https://github.com/openssl/openssl/commit/a91e537d16d74050dbde50bb0dfb1fe9930f0521https://openssl-library.org/news/secadv/20260407.txthttps://cert-portal.siemens.com/productcert/html/ssa-032379.html
2026-04-07
Published