CVE-2024-54178

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

Score 6.5 from GitHub Security Advisory published 2026-06-22. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

IBM Db2 on Cloud Pak for Data and Db2 Warehouse on Cloud Pak for Data versions 4.8,5.0,5.1,5.2,5.3 could allow an authenticated user to cause a denial of service when creating new databases due to improper allocation of resources.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
34(Track)
EG Risk 34/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
Severity65% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
15.2%
KEV
Not listed

Published

June 22, 2026

Last Modified

June 30, 2026

Advisory Details (1)

Auto-updated Jun 22, 2026
Patch available.
generic Patch Available

Security Bulletin: Multiple vulnerabilities affect IBM Db2® on Cloud Pak for Data, and Db2 Warehouse on Cloud Pak for Data.

https://www.ibm.com/support/pages/node/7277112

Vendor Advisories for CVE-2024-54178(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 67× 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.

  1. 2026-07-23 14:17 UTCEPSS rescore
  2. 2026-07-23 14:17 UTCEPSS rescore
  3. 2026-07-23 02:44 UTCEG score recompute
  4. 2026-07-22 14:07 UTCEPSS rescore
  5. 2026-07-21 15:23 UTCEPSS rescore
  6. 2026-07-20 17:07 UTCEPSS rescore
  7. 2026-07-19 14:30 UTCEPSS rescore
  8. 2026-07-19 14:30 UTCEPSS rescore
  9. 2026-07-19 02:28 UTCEPSS rescore
  10. 2026-07-19 02:28 UTCEPSS rescore
  11. 2026-07-18 10:03 UTCEPSS rescore
  12. 2026-07-16 17:02 UTCEPSS rescore
  13. 2026-07-16 12:06 UTCGHSA enrichment
  14. 2026-07-15 16:57 UTCEPSS rescore
  15. 2026-07-15 13:13 UTCGHSA enrichment
  16. 2026-07-15 01:59 UTCEPSS rescore
  17. 2026-07-15 01:59 UTCEPSS rescore
  18. 2026-07-14 14:20 UTCGHSA enrichment
  19. 2026-07-13 22:29 UTCEPSS rescore
  20. 2026-07-13 15:26 UTCGHSA enrichment
  21. 2026-07-13 06:12 UTCEPSS rescore
  22. 2026-07-12 16:31 UTCGHSA enrichment
  23. 2026-07-12 05:45 UTCEPSS rescore
  24. 2026-07-11 17:38 UTCGHSA enrichment
  25. 2026-07-11 08:26 UTCEPSS rescore
Show 46 more
  1. 2026-07-10 18:44 UTCGHSA enrichment
  2. 2026-07-09 19:51 UTCGHSA enrichment
  3. 2026-07-09 19:09 UTCEPSS rescore
  4. 2026-07-09 19:09 UTCEPSS rescore
  5. 2026-07-08 20:58 UTCGHSA enrichment
  6. 2026-07-08 15:14 UTCEPSS rescore
  7. 2026-07-07 22:05 UTCGHSA enrichment
  8. 2026-07-07 13:45 UTCEPSS rescore
  9. 2026-07-07 13:45 UTCEPSS rescore
  10. 2026-07-06 23:12 UTCGHSA enrichment
  11. 2026-07-06 16:26 UTCEPSS rescore
  12. 2026-07-06 16:26 UTCEPSS rescore
  13. 2026-07-06 02:22 UTCEPSS rescore
  14. 2026-07-06 00:18 UTCGHSA enrichment
  15. 2026-07-05 02:29 UTCEPSS rescore
  16. 2026-07-05 01:24 UTCGHSA enrichment
  17. 2026-07-04 06:30 UTCEPSS rescore
  18. 2026-07-04 06:30 UTCEPSS rescore
  19. 2026-07-04 02:30 UTCGHSA enrichment
  20. 2026-07-03 03:33 UTCGHSA enrichment
  21. 2026-07-02 04:40 UTCGHSA enrichment
  22. 2026-07-01 15:06 UTCEPSS rescore
  23. 2026-07-01 05:47 UTCGHSA enrichment
  24. 2026-06-30 23:21 UTCEPSS rescore
  25. 2026-06-30 23:21 UTCEPSS rescore
  26. 2026-06-30 06:51 UTCGHSA enrichment
  27. 2026-06-29 14:05 UTCEPSS rescore
  28. 2026-06-29 07:56 UTCGHSA enrichment
  29. 2026-06-28 14:07 UTCEPSS rescore
  30. 2026-06-28 08:58 UTCGHSA enrichment
  31. 2026-06-28 04:55 UTCEPSS rescore
  32. 2026-06-28 04:55 UTCEPSS rescore
  33. 2026-06-27 10:05 UTCGHSA enrichment
  34. 2026-06-27 03:08 UTCEPSS rescore
  35. 2026-06-27 03:07 UTCEPSS rescore
  36. 2026-06-26 11:11 UTCGHSA enrichment
  37. 2026-06-25 13:49 UTCEPSS rescore
  38. 2026-06-25 13:49 UTCEPSS rescore
  39. 2026-06-25 12:19 UTCGHSA enrichment
  40. 2026-06-24 14:04 UTCEPSS rescore
  41. 2026-06-24 14:04 UTCEPSS rescore
  42. 2026-06-24 13:25 UTCGHSA enrichment
  43. 2026-06-23 21:32 UTCEPSS rescore
  44. 2026-06-23 14:32 UTCGHSA enrichment
  45. 2026-06-22 15:37 UTCEG score recompute
  46. 2026-06-22 15:37 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-54178?
CVE-2024-54178 is a medium vulnerability published on June 22, 2026. IBM Db2 on Cloud Pak for Data and Db2 Warehouse on Cloud Pak for Data versions 4.8,5.0,5.1,5.2,5.3 could allow an authenticated user to cause a denial of service when creating new databases due to improper allocation of resources.
When was CVE-2024-54178 disclosed?
CVE-2024-54178 was first published in the National Vulnerability Database on June 22, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-54178 actively exploited?
CVE-2024-54178 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 15.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-54178?
CVE-2024-54178 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2024-54178?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-54178, 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-2024-54178

Explore →

Is Your Infrastructure Affected by CVE-2024-54178?

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

Start Free Scan →Browse All CVEs