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
Trending — 3 sources updated this week
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.8Exploit: NoneExposed: 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
13.3%
KEV
Not listed

Published

April 7, 2026

Last Modified

May 12, 2026

Advisory Details (6)

Auto-updated May 10, 2026
No patch confirmed yet.
generic

Avoid possible buffer overflow in buf2hex conversion · openssl/openssl@a91e537 · GitHub

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

Avoid possible buffer overflow in buf2hex conversion · openssl/openssl@a242160 · GitHub

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

Avoid possible buffer overflow in buf2hex conversion · openssl/openssl@945b935 · GitHub

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

Avoid possible buffer overflow in buf2hex conversion · openssl/openssl@7a9087e · GitHub

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

Avoid possible buffer overflow in buf2hex conversion · openssl/openssl@364f095 · GitHub

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.

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 15× in last 7d / 47× 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 151 total refreshes for this CVE.

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

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 May 12, 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 13.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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.