CVE-2026-63074

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreHIGH confidence

Score 5.9 from GitHub Security Advisory published 2026-08-25. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — Patch released this week
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: None knownExposed: 0

A fix is available — apply it.

Issue summary: The OpenSSL Certificate Management Protocol (CMP) caches additional certificates (extraCerts) sent in a CMP message, but never expunges them (for instance if they are invalid). If a server reuses an OSSL_CMP_CTX frequently, this cache of extraCerts may grow unboundedly, and a malicious client may flood a CMP server with requests driving this growth.

Impact summary: Users utilizing a CMP server that reuses a single OSSL_CMP_CTX for the lifetime of a server process may observe unbounded memory growth in the event a malicious client repeatedly sends requests containing unique extra certificates, which may lead to OOM conditions.

CWE: CWE-770: Allocation of Resources Without Limits or Throttling

Description: If a remote user sends CMP messages to a server with a list of extraCerts and the message is rejected, the extraCerts from the message remains in the server contexts untrusted certificate stack. This exposes servers with long lived ctx objects to Denial of Service attacks in which an attacker sends messages intending to be rejected with a large list of additional certificates repeatedly, forcing the server to store them indefinitely. The issue was fixed by removing the added extra certs if the message is rejected, using the same method as when the context is configured to not do caching at all.

FIPS impact: no As the CMP code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.

CVSS v3
5.9
EG Score
5.9(high)
EG Risk
27(Track)
EG Risk 27/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
Severity59% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
42%
KEV
Not listed

Published

August 25, 2026

Last Modified

September 11, 2026

Advisory Details (6)

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

commit 21a5d9658b0c (openssl/openssl)

Fix landed in openssl/openssl commit 21a5d9658b0c — awaiting tagged release

https://github.com/openssl/openssl/commit/21a5d9658b0c66daace60e10ea18ff32a448de9f
github_commit

commit f636f9ca0fa1 (openssl/openssl)

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

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

commit 75360af9650d (openssl/openssl)

Fix landed in openssl/openssl commit 75360af9650d — awaiting tagged release

https://github.com/openssl/openssl/commit/75360af9650d4e0c82ba0050c5c9912cd79e54af
github_commit

commit 01e567978a55 (openssl/openssl)

Fix landed in openssl/openssl commit 01e567978a55 — awaiting tagged release

https://github.com/openssl/openssl/commit/01e567978a55fba18142a230380c31296049fae7
github_commit

commit 74ae7f6df47a (openssl/openssl)

Fix landed in openssl/openssl commit 74ae7f6df47a — awaiting tagged release

https://github.com/openssl/openssl/commit/74ae7f6df47a5767c1010b88c47507dfc5b32c46
generic
https://openssl-library.org/news/secadv/20260825.txt

Vendor Advisories for CVE-2026-63074(5)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenssl-provider-legacy (3.5.5-1ubuntu3.4) @ resolute2026-09-19ubuntu
redhatopenssl-1:3.5.8-1.el10_22026-09-14redhat
redhatopenssl-1:3.5.8-1.el9_82026-09-14redhat
redhatopenssl3-main-3.5.8-0.1.hum12026-08-25redhat
redhatopenssl-main-3.5.8-0.1.hum12026-08-25redhat

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

(6 across 6 ecosystems)
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
openssl—3.5.8-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
openssl—3.5.8-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
openssl—3.5.8-r0—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
openssl3.0.10-1 ... 4.0.2-1 (86 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.1-1 ... 3.5.7-1~deb13u1 (13 versions)3.5.7-1~deb13u2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.1-1 ... 4.0.2-1 (28 versions)——

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 26× in last 7d / 102× 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 102 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-63074?
CVE-2026-63074 is a medium vulnerability published on August 25, 2026. Issue summary: The OpenSSL Certificate Management Protocol (CMP) caches additional certificates (extraCerts) sent in a CMP message, but never expunges them (for instance if they are invalid). If a server reuses an OSSLCMPCTX frequently, this cache of extraCerts may grow unboundedly, and a malicious…
When was CVE-2026-63074 disclosed?
CVE-2026-63074 was first published in the National Vulnerability Database on August 25, 2026, with the most recent update on September 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63074 actively exploited?
CVE-2026-63074 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 58.5% of all scored CVEs.
What is the CVSS score of CVE-2026-63074?
CVE-2026-63074 has a CVSS v3.1 base score of 5.9 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-63074?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63074, 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-63074

Explore →

Is Your Infrastructure Affected by CVE-2026-63074?

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

Start Free Scan →Browse All CVEs