CVE-2026-31789: Heap Buffer Overflow in Hexadecimal Conversion

Published Apr 7, 2026
·
Updated

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

7 affected componentsFixes available
Microsoft azl3 openssl 3.3.5-4
OpenSSL OpenSSL>=3.0.0<3.0.20
OpenSSL OpenSSL>=3.3.0<3.3.7
OpenSSL OpenSSL>=3.4.0<3.4.5
OpenSSL OpenSSL>=3.5.0<3.5.6
OpenSSL OpenSSL>=3.6.0<3.6.2
IBM API Connect<=V10.0.8.0 - V10.0.8.9

Event History

Apr 7, 2026
CVE Published
via MITRE·10:00 PM
Data Sourced
via MITRE·10:00 PM
DescriptionWeakness
Data Sourced
via NVD·10:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Apr 9, 2026
Data Sourced
via Microsoft·08:02 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:02 AM
DescriptionSeverity
Jul 7, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203