Threat Feed

CVE-2026-121481: Integer Overflow in EVP_EncodeBlock() with Very Large Input Lengths

Exploitation: None known · CVSS 9.8 Critical · Unauthenticated · Published 2026-11-18

Description

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.

Enclave's analysis

EVP_EncodeBlock() does signed-integer math on the output size, and if you hand it an input buffer close to 2GiB that math overflows, so it writes past the caller's output buffer. The only documented way to reach this is a local openssl s_client command fed a huge proxy_pass value through an environment variable with the GOST engine turned on — not a generic network trigger, despite the network-based CVSS score. A core OpenSSL maintainer called that reproducer synthetic and questioned whether it reflects real-world use. Upgrade to 4.0.4 or 4.1.1; don't expect this to be remotely reachable in typical deployments.

Fix

Upgrade to 4.1.1 or 4.0.4, whichever matches your release line.

Vendor advisory

Affected versions

ProductVulnerableFixed in
OpenSSL4.1.0 before 4.1.14.1.1
OpenSSL4.0.0 before 4.0.44.0.4

Seen in 3 sources