Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
9.8
OpenSSL can crash processing oversized certificate fields
published 1 day ago
Summary
OpenSSL may overflow memory when it converts extremely large data in a certificate to a hex string, which can cause the application to stop working or, in rare cases, let an attacker run code. The problem only appears on 32‑bit systems and requires a certificate larger than a gigabyte, so it is unlikely in normal use. Upgrade OpenSSL to a version that fixes the issue or avoid handling untrusted certificates on 32‑bit platforms.
What to do
- Update docker hardened images openssl to version 3.5.6-r0.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| Docker Hardened Images:Alpine:3.23 | docker hardened images | openssl-provider-fips | All versions |
| Docker Hardened Images:Alpine:3.23 | docker hardened images | openssl |
< 3.5.6-r0 Fix: upgrade to 3.5.6-r0
|
Original advisory text
Issue summary: Converting an excessively large OCTET STRING value to
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.
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.
References
- https://scout.docker.com/v/DHI-j2mz-5khr-oxz6-t3hk Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-31789 Vendor Advisory
- https://openssl-library.org/news/secadv/20260407.txt Vendor Advisory
- https://github.com/openssl/openssl/commit/a91e537d16d74050dbde50bb0dfb1fe9930f05... Patch
- https://github.com/openssl/openssl/commit/a24216018e1ede8ff01a4ff5afff7dfbd443e2... Patch
- https://github.com/openssl/openssl/commit/945b935ac66cc7f1a41f1b849c7c25adb5351f... Patch
- https://github.com/openssl/openssl/commit/7a9087efd769f362ad9c0e30c7baaa6bbfa65e... Patch
- https://github.com/openssl/openssl/commit/364f095b80601db632b0def6a33316967f863b... Patch
- https://security.alpinelinux.org/vuln/CVE-2026-31789 Vendor Advisory
- https://security-tracker.debian.org/tracker/CVE-2026-31789 Vendor Advisory
- https://ubuntu.com/security/CVE-2026-31789 Vendor Advisory
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-31789 Vendor Advisory
Internet-facing
3 days
Internal
60 days
- Not known to be exploited
- Can be exploited automatically (estimated)
- Gives an attacker full control (estimated)
Timeline
Published20 Nov 2026
Updated20 Nov 2026
First seen20 Nov 2026
Sources
DHI-j2mz-5khr-oxz6-t3hk · OSV
Track software like this
Free during beta