may overflow the calculation of the encoded output size and write past the end
of the caller-supplied output buffer.
Impact summary: No path by which an attacker can trigger this has been
identified. An application that passes an input length near INT_MAX to
EVP_EncodeBlock() could suffer a heap buffer overflow, crashing or corrupting
its own memory, but it must itself supply such a length.
CWE: CWE-190: Integer Overflow or Wraparound
Description: EVP_EncodeBlock() base64-encodes a buffer of a caller-supplied
length into an output buffer that the caller allocates. The caller is expected
to reserve 4*((len+2)/3)+1 bytes. For input lengths close to INT_MAX, the
arithmetic that computes the encoded length overflows a signed integer, so the
function writes more data than the documented output size. The result is a
heap buffer overflow in the calling process.
Reaching this requires an application to pass an input length near INT_MAX to
EVP_EncodeBlock(). OpenSSL's TLS, QUIC and CMS implementations never encode
buffers of that size, and the command line tools cannot practically be made to
do so: the limits on reading a proxy password from a file and on bignum sizes
prevent it. An application that accepts an attacker-controlled length and
forwards it to EVP_EncodeBlock() without its own bound check is exposed.
The severity is Low because no attacker-controlled path to the overflow is
known. The caller must already hold a buffer of about two gigabytes before the
defect can be reached.
FIPS impact: no
The affected code is outside the FIPS module boundary.
Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Sat, 21 Nov 2026 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Redhat
Redhat hummingbird |
|
| CPEs | cpe:/a:redhat:hummingbird:1 | |
| Vendors & Products |
Redhat
Redhat hummingbird |
|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Fri, 20 Nov 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
cvssV3_1
|
Fri, 20 Nov 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-122 | |
| Metrics |
cvssV3_1
|
cvssV3_1
|
Fri, 20 Nov 2026 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-680 |
Fri, 20 Nov 2026 10:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Calling 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. | Issue summary: Calling 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. Impact summary: No path by which an attacker can trigger this has been identified. An application that passes an input length near INT_MAX to EVP_EncodeBlock() could suffer a heap buffer overflow, crashing or corrupting its own memory, but it must itself supply such a length. CWE: CWE-190: Integer Overflow or Wraparound Description: EVP_EncodeBlock() base64-encodes a buffer of a caller-supplied length into an output buffer that the caller allocates. The caller is expected to reserve 4*((len+2)/3)+1 bytes. For input lengths close to INT_MAX, the arithmetic that computes the encoded length overflows a signed integer, so the function writes more data than the documented output size. The result is a heap buffer overflow in the calling process. Reaching this requires an application to pass an input length near INT_MAX to EVP_EncodeBlock(). OpenSSL's TLS, QUIC and CMS implementations never encode buffers of that size, and the command line tools cannot practically be made to do so: the limits on reading a proxy password from a file and on bignum sizes prevent it. An application that accepts an attacker-controlled length and forwards it to EVP_EncodeBlock() without its own bound check is exposed. The severity is Low because no attacker-controlled path to the overflow is known. The caller must already hold a buffer of about two gigabytes before the defect can be reached. FIPS impact: no The affected code is outside the FIPS module boundary. |
| Title | Integer Overflow in EVP_EncodeBlock() with Very Large Input Lengths | |
| Weaknesses | CWE-190 |
Fri, 20 Nov 2026 05:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Thu, 19 Nov 2026 22:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-122 | |
| Metrics |
cvssV3_1
|
Thu, 19 Nov 2026 14:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-680 |
Thu, 19 Nov 2026 04:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Potential Buffer Overflow in EVP_EncodeBlock with Large Input Length in OpenSSL | |
| Weaknesses | CWE-680 |
Wed, 18 Nov 2026 17:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Potential Buffer Overflow in EVP_EncodeBlock with Large Input Length in OpenSSL | |
| Weaknesses | CWE-680 |
Wed, 18 Nov 2026 13:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Openssl
Openssl openssl |
|
| Vendors & Products |
Openssl
Openssl openssl |
Wed, 18 Nov 2026 11:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Calling 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. | |
| References |
|
Status: PUBLISHED
Assigner: openssl
Published:
Updated: 2026-11-20T19:45:11.949Z
Reserved: 2026-11-03T13:45:42.894Z
Link: CVE-2026-121481
No data.
Status : Awaiting Analysis
Published: 2026-11-18T12:17:04.313
Modified: 2026-11-20T20:17:13.820
Link: CVE-2026-121481
OpenCVE Enrichment
Updated: 2026-11-21T02:45:01Z