Skip to content
NewA calmer, faster ZeroHour

CVE-2026-121481

Heap overflow in OpenSSL EVP_EncodeBlock near INT_MAX

CVSS 3.1
5.9 medium
EPSS
<1%p41
Published
·
Modified
Analyze CVE-2026-121481 with Vani AIImpact, affected versions, exploitation status, mitigations and detection

OpenSSL EVP_EncodeBlock() can overflow its encoded-output size calculation when the input length is close to INT_MAX and write past the caller-supplied buffer. Any code that passes an input of that size can corrupt heap memory beyond the buffer. OpenSSL has not listed affected or fixed versions.

What to do: Apply OpenSSL's update for CVE-2026-121481. Affected and fixed versions have not been listed.

ProductAffected
OpenSSL—
Estimated exposure
No basis for an estimate.

Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.

Description · NVD

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.

Weakness
CWE-190
Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

In the news

2 stories