CVE-2026-34180

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-09. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

Issue summary: Parsing a crafted DER-encoded ASN.1 structure with a primitive element whose content exceeds 2 gigabytes in length may cause a heap buffer over-read on 64-bit Unix and Unix-like platforms.

Impact summary: The heap buffer over-read may crash the application (Denial of Service) or to load into the decoded ASN.1 object contents of memory beyond the end of the input buffer. More typically such ASN.1 elements would instead be truncated.

An integer truncation in OpenSSL's ASN.1 decoder causes the content length of an ASN.1 primitive element to be mishandled when it exceeds 2 gigabytes. In the worst case the truncated length is treated as a request to scan the binary content for a terminating zero byte, possibly causing OpenSSL to read either less than or beyond the end of the allocated buffer.

Applications that pass attacker-supplied data to d2i_X509(), d2i_PKCS7(), or any other d2i_* decoding function are affected. OpenSSL's own command-line tools are not vulnerable, as data read through the BIO layer is checked before it reaches the affected code. The issue only affects 64-bit Unix and Unix-like platforms; 32-bit platforms and 64-bit Windows are not affected.

The FIPS modules in 4.0, 3.6, 3.5, 3.4 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
39(Track)
EG Risk 39/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
Severity75% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
61%
KEV
Not listed

Published

June 9, 2026

Last Modified

July 23, 2026

Advisory Details (1)

Auto-updated Jun 9, 2026
No patch confirmed yet.

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenssl (1.0.1f-1ubuntu2.27+esm14) @ trusty2026-08-21ubuntu
ubuntuopenssl-provider-legacy (3.5.5-1ubuntu3.2) @ resolute2026-08-21ubuntu
redhatinsights-proxy/insights-proxy-container-rhel9:17828905032026-07-01redhat
redhatdiscovery/discovery-ui-rhel9:17821669522026-06-24redhat
redhatrhui5/rhua-rhel9:17815257392026-06-16redhat
redhatopenssl-1:3.5.5-4.el9_82026-06-11redhat
redhatopenssl-1:3.5.5-4.el10_22026-06-11redhat

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

(7 across 7 ecosystems)
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.7-r0
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.7-r0
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.7-r0
Debian:11(1)
PackageVulnerable rangeFixed inDependents
openssl1.1.1k-1 ... 1.1.1w-0~deb11u1 (23 versions)1.1.1w-0+deb11u8
Debian:12(1)
PackageVulnerable rangeFixed inDependents
openssl3.0.10-1 ... 3.0.9-1 (22 versions)3.0.20-1~deb12u2
Debian:13(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.1-1 ... 3.5.6-1~deb13u1 (11 versions)3.5.6-1~deb13u2
Debian:14(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.1-1 ... 3.6.2-1 (19 versions)3.6.3-1

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

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 31× in last 7d / 145× 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 323 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-34180?
CVE-2026-34180 is a high vulnerability published on June 9, 2026. Issue summary: Parsing a crafted DER-encoded ASN.1 structure with a primitive element whose content exceeds 2 gigabytes in length may cause a heap buffer over-read on 64-bit Unix and Unix-like platforms. Impact summary: The heap buffer over-read may crash the application (Denial of Service) or to…
When was CVE-2026-34180 disclosed?
CVE-2026-34180 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-34180 actively exploited?
CVE-2026-34180 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 39.1% of all scored CVEs.
What is the CVSS score of CVE-2026-34180?
CVE-2026-34180 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-34180?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-34180, 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-34180

Explore →

Is Your Infrastructure Affected by CVE-2026-34180?

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