OpenSSL Patches Critical Heap Buffer Overflow in EVP_EncodeBlock (CVE-2026-121481)
OpenSSL 4.1.1 fixes a CVSS 9.8 pre-authentication heap buffer overflow in the base64 encoder. The flaw affects all 4.1.x versions and can be triggered remotely via crafted input to EVP_EncodeBlock.

By Elena Rostova, Cybersecurity
3 min read
OpenSSL 4.1.1 fixes critical pre-auth RCE in base64 encoder
The OpenSSL project released version 4.1.1 on 17 November 2026 to address CVE-2026-121481, a critical heap buffer overflow in the EVP_EncodeBlock() function used for base64 encoding. The vulnerability carries a CVSS 9.8 score and can be triggered remotely without authentication.
What the vulnerability does
EVP_EncodeBlock() is a low-level API that encodes binary data to base64. The flaw occurs when the function processes specially crafted input that causes a heap buffer overflow during encoding. Because base64 encoding is used in many protocols (TLS certificates, email, JWT tokens, API authentication), an attacker who can supply controlled input to a vulnerable application may achieve remote code execution.
The OpenSSL security advisory states the issue affects all OpenSSL 4.1.x releases prior to 4.1.1. The 3.x and 1.1.1 long-term support branches are not affected.
Technical details
The fix was merged in pull request #33652 on the OpenSSL GitHub repository. The patch adds bounds checking to the EVP_EncodeBlock() implementation to prevent the heap overflow when processing malformed input lengths.
The vulnerability was discovered through fuzzing and reported responsibly to the OpenSSL security team. The advisory was published at openssl.org/news/secadv/20261117.txt.
Impact and action required
Any application linking against OpenSSL 4.1.0 and calling EVP_EncodeBlock() directly or indirectly (via higher-level APIs that use base64 encoding) is potentially exposed. Common scenarios include:
TLS certificate parsing and validation
JWT token encoding/decoding
Email message processing (MIME base64)
API authentication headers
Configuration file parsing
Immediate action: Upgrade to OpenSSL 4.1.1. The release is available from the OpenSSL downloads page and through distribution package managers.
Why this matters
OpenSSL is the most widely deployed TLS library. A pre-authentication RCE in a core encoding function is a severe supply-chain risk. While exploitation requires an attacker to control input to EVP_EncodeBlock(), the ubiquity of base64 in network protocols means many code paths are reachable remotely. Organisations running OpenSSL 4.1.0 should prioritise this update.
Sources
- 1OpenSSL Security Advisory 20261117openssl.org
- 2GitHub Pull Request #33652 (fix)github.com
- 3OpenSSL Vulnerabilities Pageopenssl.org
- 4Hacker News Discussionnews.ycombinator.com