OpenSSL Hit by Critical 9.8 Heap Buffer Overflow Vulnerability in Base64 Encoding Function

Blog WriterCybersecurity News - Original News Source is cybersecuritynews.com


A heap buffer overflow in OpenSSL’s Base64 encoding function can corrupt application memory when the library processes very large inputs. The flaw, tracked as CVE-2026-121481, was published on November 18, 2026, with a critical CVSS 3.1 score of 9.8.

That score describes the potential severity, but it does not mean every service that uses OpenSSL is remotely exposed.

The flaw affects EVP_EncodeBlock(), which converts binary data into printable text. Base64 produces four output bytes for every three input bytes, with padding for a partial group. The application supplies the buffer that holds the result.

For very large inputs, OpenSSL’s calculation of the encoded length can exceed the range of the integer used to store it. That calculation error can cause the encoder to write beyond the end of the supplied buffer. The write can corrupt nearby memory or crash the application.

OpenSSL Heap Buffer Overflow Vulnerability

This differs from the OpenSSL flaw that could leak server memory: the Base64 bug writes outside a buffer, while the earlier DTLS flaw read data outside one.

The key question for security teams is whether an application passes large amounts of untrusted data to the affected encoder. A server’s use of OpenSSL for encrypted connections does not, by itself, answer that question.

Teams should check where their applications call the function and which size limits apply before encoding begins. The CVE version record lists OpenSSL 4.0.0 through 4.0.3 and OpenSSL 4.1.0 as affected, with 4.0.4 and 4.1.1 marking the upper bounds of those ranges.

OpenSSL branch Affected versions First fixed version
4.0.x 4.0.0 through 4.0.3, inclusive 4.0.4
4.1.x 4.1.0 4.1.1
3.x Outside the affected ranges in the upstream CVE record Not applicable

Those version numbers do not, by themselves, confirm that a fixed package is available from a particular vendor. As with earlier OpenSSL memory corruption fixes, check the release or package notes for the branch you run.

Ubuntu’s security tracker assigns the issue Medium priority and lists its main openssl packages as needing evaluation. It also marks the nodejs package in Ubuntu 22.04 LTS as vulnerable.

Ubuntu notes that this package embeds its own copy of OpenSSL, so checking only the system library can miss software that bundles it.

Inventory OpenSSL copies in system packages, containers, and application bundles. Prioritize applications that Base64-encode data supplied by users or external services.

Until a vendor-confirmed update is available, enforce application-level input limits before encoding. After updating, restart or redeploy affected workloads and verify that they are running the updated build.

For developers, the OpenSSL encoding documentation explains that callers must reserve space for the encoded data and a final zero byte that marks the end of the string. Review that calculation alongside input limits. For large files, consider an encoding interface that processes data in chunks rather than passing the whole file to one call.

What Are Leading Organizations Doing About AI and Cyber Risks? Find Out. View Details!

The post OpenSSL Hit by Critical 9.8 Heap Buffer Overflow Vulnerability in Base64 Encoding Function appeared first on Cyber Security News.