Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
9.8
CVE-2026-121481: OpenSSL base64 encoding can overflow output buffer
CVE-2026-121481 · published 1 day ago
Summary
The OpenSSL library's base64 encoding routine may miscalculate the size of the output when given an extremely large input, causing it to write past the end of the allocated buffer. This can crash the application that uses it, but only if the application itself supplies such a massive input length. Ensure any software that uses OpenSSL checks input sizes before calling the encoding function, and apply the latest OpenSSL updates where the calculation has been corrected.
What to do
- Update openssl openssl to version 4.1.1 or later.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| – | openssl | openssl | < 4.1.1 |
| Ubuntu:Pro:14.04:LTS | canonical | openssl | All versions |
| Ubuntu:Pro:16.04:LTS | canonical | edk2 | All versions |
| Ubuntu:Pro:16.04:LTS | canonical | nodejs | All versions |
| Ubuntu:Pro:18.04:LTS | canonical | openssl1.0 | All versions |
| Ubuntu:Pro:FIPS-preview:22.04:LTS | canonical | openssl-fips | All versions |
| Ubuntu:26.10 | canonical | edk2-hwe | All versions |
Original advisory text
CVE-2026-121481 does not affect BellSoft software
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.
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.
References
- https://github.com/openssl/openssl/pull/33652 patch
- https://ubuntu.com/security/CVE-2026-121481 Third Party Advisory
- https://www.cve.org/CVERecord?id=CVE-2026-121481 Third Party Advisory
- https://news.ycombinator.com/item?id=50569226
- https://docs.bell-sw.com/security/cves/CVE-2026-121481 Vendor Advisory
Severity
9.8
Critical
Type
CWE-122Heap-based Buffer Overflow
CWE-190Integer Overflow
Timeline
Published20 Nov 2026
Updated21 Nov 2026
First seen18 Nov 2026
Sources
CVE-2026-121481 · NVD
CVE-2026-121481 · MITRE
UBUNTU-CVE-2026-121481 · OSV
BELL-CVE-2026-121481 · OSV
Track software like this
Free during beta