OpenSSL’s EVP_EncodeBlock() can write past its supplied buffer on very large inputs because of an encoded-length calculation error, corrupting memory or crashing the application.
The flaw affects 4.0.0–4.0.3 and 4.1.0; fixes are in 4.0.4 and 4.1.1.
The issue was published on November 18, 2026 and received a high severity rating of 9,8 out of 10. The issue occurs when an application processes extremely large amounts of data. During conversion, an error in calculating the required space can lead to the program writing data beyond the allowed memory limits. This can cause data corruption in system memory or an unexpected application shutdown.
Who is affected and what applies?
A high score indicates the maximum theoretical severity of the issue, but this does not mean that every service that uses OpenSSL is automatically at risk. The issue mainly concerns cases where applications feed this function with very large data from external sources.
According to official data, OpenSSL versions 4.0.0 to 4.0.3, as well as version 4.1.0, are affected. Versions 4.0.4 and 4.1.1 fix the problem. Older versions 3.x are outside the affected range.
↳
READ ALSO
HACKS.GR / RELATED
Vulnerabilities & Security Updates
SonicWall urges immediate replacement of old firewalls due to security risks
↗
However, checking only the official system versions is not enough. Some programs, such as the nodejs package in Ubuntu 22.04 LTS, may have their own separate copy of OpenSSL embedded within them. Ubuntu has marked the issue as medium priority and is reviewing its packages.
What administrators should pay attention to
Technology teams are urged to identify all copies of OpenSSL present in their systems, packages, and applications. It is recommended to limit the size of data that applications accept before processing it. After applying the updates, administrators should restart their systems and services to ensure they are using the safe version.
>Stay connected with Hacks.gr
Set us as a preferred source on Google and find us on social media.
Preferred source
↗
end of article
Top comments (0)