CVE-2026-31789: Heap Buffer Overflow in Hexadecimal Conversion
Heap Buffer Overflow in Hexadecimal Conversion
Other sources
Issue summary: Converting an excessively large OCTET STRING value to a hexadecimal string leads to a heap buffer overflow on 32 bit platforms.
Impact summary: A heap buffer overflow may lead to a crash or possibly an attacker controlled code execution or other undefined behavior.
If an attacker can supply a crafted X.509 certificate with an excessively large OCTET STRING value in extensions such as the Subject Key Identifier (SKID) or Authority Key Identifier (AKID) which are being converted to hex, the size of the buffer needed for the result is calculated as multiplication of the input length by 3. On 32 bit platforms, this multiplication may overflow resulting in the allocation of a smaller buffer and a heap buffer overflow.
Applications and services that print or log contents of untrusted X.509 certificates are vulnerable to this issue. As the certificates would have to have sizes of over 1 Gigabyte, printing or logging such certificates is a fairly unlikely operation and only 32 bit platforms are affected, this issue was assigned Low severity.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
— NVD
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-31789?
CVE-2026-31789 has a high severity due to its potential to cause a heap buffer overflow leading to application crashes.
How do I fix CVE-2026-31789?
To fix CVE-2026-31789, update to the patched version of the affected software, specifically Microsoft azl3 openssl 3.3.5-4.
What platforms are affected by CVE-2026-31789?
CVE-2026-31789 specifically affects 32-bit platforms due to the heap buffer overflow in hexadecimal conversions.
What is the impact of CVE-2026-31789?
The impact of CVE-2026-31789 includes potential application crashes and vulnerabilities to exploits through buffer overflow.
Can CVE-2026-31789 be exploited remotely?
Yes, CVE-2026-31789 can potentially be exploited remotely if the vulnerable software processes user input without proper validation.