CVE-2026-31789

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-04-08. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

April 7, 2026

Last Modified

July 24, 2026

Advisory Details (7)

Auto-updated Sep 12, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit

commit a91e537d16d7 (openssl/openssl)

Fix landed in openssl/openssl commit a91e537d16d7 — awaiting tagged release

https://github.com/openssl/openssl/commit/a91e537d16d74050dbde50bb0dfb1fe9930f0521
github_commit

commit a24216018e1e (openssl/openssl)

Fix landed in openssl/openssl commit a24216018e1e — awaiting tagged release

https://github.com/openssl/openssl/commit/a24216018e1ede8ff01a4ff5afff7dfbd443e2f9
github_commit

commit 945b935ac66c (openssl/openssl)

Fix landed in openssl/openssl commit 945b935ac66c — awaiting tagged release

https://github.com/openssl/openssl/commit/945b935ac66cc7f1a41f1b849c7c25adb5351f49
github_commit

commit 7a9087efd769 (openssl/openssl)

Fix landed in openssl/openssl commit 7a9087efd769 — awaiting tagged release

https://github.com/openssl/openssl/commit/7a9087efd769f362ad9c0e30c7baaa6bbfa65ecf
github_commit

commit 364f095b8060 (openssl/openssl)

Fix landed in openssl/openssl commit 364f095b8060 — awaiting tagged release

https://github.com/openssl/openssl/commit/364f095b80601db632b0def6a33316967f863bde

Vendor Advisories for CVE-2026-31789(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenssl (3.0.2-0ubuntu1.23) @ jammy2026-06-12ubuntu
redhatopenssl-main-3.5.6-0.1.hum12026-04-09redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(8 across 8 ecosystems)
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
openssl3.3.7-r0
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
openssl3.3.7-r0
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.6-r0
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.6-r0
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.6-r0
Debian:12(1)
PackageVulnerable rangeFixed inDependents
openssl3.0.10-1 ... 3.0.9-1 (20 versions)3.0.19-1~deb12u2
Debian:13(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.1-1 ... 3.5.5-1~deb13u1 (8 versions)3.5.5-1~deb13u2
Debian:14(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.1-1 ... 3.6.1-3 (20 versions)3.6.2-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 290 total refreshes for this CVE.

  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-12 15:01 UTCEPSS rescore
  3. 2026-09-11 14:52 UTCEPSS rescore
  4. 2026-09-10 09:34 UTCEPSS rescore
  5. 2026-09-08 22:00 UTCEPSS rescore
  6. 2026-09-07 16:01 UTCEPSS rescore
  7. 2026-09-06 13:47 UTCEPSS rescore
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-04 05:06 UTCEPSS rescore
  10. 2026-09-02 23:29 UTCOSV refresh
  11. 2026-09-02 14:11 UTCEPSS rescore
  12. 2026-09-01 13:53 UTCEPSS rescore
  13. 2026-09-01 04:39 UTCEPSS rescore
  14. 2026-09-01 04:39 UTCEPSS rescore
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-24 14:17 UTCEPSS rescore
  22. 2026-08-21 23:49 UTCEPSS rescore
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-19 17:03 UTCEPSS rescore
Show 75 more
  1. 2026-08-18 13:48 UTCEPSS rescore
  2. 2026-08-17 13:47 UTCEPSS rescore
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-16 12:17 UTCVendor advisory
  5. 2026-08-16 12:17 UTCGHSA enrichment
  6. 2026-08-16 07:54 UTCEG score recompute
  7. 2026-08-16 07:54 UTCVendor advisory
  8. 2026-08-16 07:53 UTCGHSA enrichment
  9. 2026-08-16 02:14 UTCEPSS rescore
  10. 2026-08-15 01:30 UTCEPSS rescore
  11. 2026-08-14 22:56 UTCVendor advisory
  12. 2026-08-14 22:56 UTCGHSA enrichment
  13. 2026-08-14 18:32 UTCVendor advisory
  14. 2026-08-14 18:32 UTCGHSA enrichment
  15. 2026-08-14 14:09 UTCVendor advisory
  16. 2026-08-14 14:09 UTCGHSA enrichment
  17. 2026-08-14 09:45 UTCVendor advisory
  18. 2026-08-14 09:45 UTCGHSA enrichment
  19. 2026-08-14 05:22 UTCEG score recompute
  20. 2026-08-14 05:22 UTCVendor advisory
  21. 2026-08-14 05:22 UTCGHSA enrichment
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-13 09:37 UTCVendor advisory
  24. 2026-08-13 09:37 UTCGHSA enrichment
  25. 2026-08-13 04:24 UTCVendor advisory
  26. 2026-08-13 04:24 UTCGHSA enrichment
  27. 2026-08-13 00:00 UTCVendor advisory
  28. 2026-08-13 00:00 UTCGHSA enrichment
  29. 2026-08-12 19:37 UTCEG score recompute
  30. 2026-08-12 19:37 UTCVendor advisory
  31. 2026-08-12 19:37 UTCGHSA enrichment
  32. 2026-08-12 13:50 UTCEPSS rescore
  33. 2026-08-12 00:14 UTCVendor advisory
  34. 2026-08-12 00:14 UTCGHSA enrichment
  35. 2026-08-11 19:49 UTCEG score recompute
  36. 2026-08-11 19:49 UTCVendor advisory
  37. 2026-08-11 19:49 UTCGHSA enrichment
  38. 2026-08-11 07:35 UTCVendor advisory
  39. 2026-08-11 07:35 UTCGHSA enrichment
  40. 2026-08-11 03:11 UTCEG score recompute
  41. 2026-08-11 03:11 UTCVendor advisory
  42. 2026-08-11 03:11 UTCGHSA enrichment
  43. 2026-08-11 00:00 UTCEPSS rescore
  44. 2026-08-10 11:56 UTCVendor advisory
  45. 2026-08-10 11:56 UTCGHSA enrichment
  46. 2026-08-10 06:24 UTCVendor advisory
  47. 2026-08-10 06:24 UTCGHSA enrichment
  48. 2026-08-10 02:01 UTCVendor advisory
  49. 2026-08-10 02:01 UTCGHSA enrichment
  50. 2026-08-09 21:37 UTCVendor advisory
  51. 2026-08-09 21:37 UTCGHSA enrichment
  52. 2026-08-09 17:14 UTCEG score recompute
  53. 2026-08-09 17:14 UTCVendor advisory
  54. 2026-08-09 17:14 UTCGHSA enrichment
  55. 2026-08-09 13:46 UTCEPSS rescore
  56. 2026-08-09 12:50 UTCVendor advisory
  57. 2026-08-09 12:50 UTCGHSA enrichment
  58. 2026-08-09 04:53 UTCEG score recompute
  59. 2026-08-09 04:53 UTCVendor advisory
  60. 2026-08-09 04:53 UTCGHSA enrichment
  61. 2026-08-08 16:37 UTCEPSS rescore
  62. 2026-08-08 08:26 UTCVendor advisory
  63. 2026-08-08 08:26 UTCGHSA enrichment
  64. 2026-08-08 04:03 UTCVendor advisory
  65. 2026-08-08 04:03 UTCGHSA enrichment
  66. 2026-08-07 23:39 UTCVendor advisory
  67. 2026-08-07 23:39 UTCGHSA enrichment
  68. 2026-08-07 19:16 UTCEG score recompute
  69. 2026-08-07 19:16 UTCVendor advisory
  70. 2026-08-07 19:16 UTCGHSA enrichment
  71. 2026-08-07 14:53 UTCVendor advisory
  72. 2026-08-07 14:52 UTCGHSA enrichment
  73. 2026-08-06 17:35 UTCVendor advisory
  74. 2026-08-06 17:35 UTCGHSA enrichment
  75. 2026-08-06 13:09 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-31789?
CVE-2026-31789 is a critical vulnerability published on April 7, 2026. 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…
When was CVE-2026-31789 disclosed?
CVE-2026-31789 was first published in the National Vulnerability Database on April 7, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31789 actively exploited?
CVE-2026-31789 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 84.4% of all scored CVEs.
What is the CVSS score of CVE-2026-31789?
CVE-2026-31789 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-31789?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31789, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31789

Explore →

Is Your Infrastructure Affected by CVE-2026-31789?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.