CVE-2026-63308

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 80% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this weekElevated
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

Helm through 4.2.3, fixed in commit ba6c9a2, contains a denial of service vulnerability in the Files.Lines template helper in pkg/engine/files.go that allows attackers to trigger an index out of range panic by including zero-length byte slices in chart files. Attackers can include empty files in Helm charts to cause deterministic render failures across template, install, upgrade, lint, and SDK Engine.Render operations.

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

Published

July 17, 2026

Last Modified

July 30, 2026

Advisory Details (4)

Auto-updated Jul 17, 2026
🔬 Proof of concept available. Upstream fix merged — awaiting tagged release. Sources: github_pr, github_commit.
generic

Chat2DB < 5.3.0 Insecure Direct Object Reference via GET /api/connection/datasource | Advisories | VulnCheck

https://www.vulncheck.com/advisories/chat2db-insecure-direct-object-reference-via-get-api-connection-datasource
github_commit

commit ba6c9a29efa7 (helm/helm)

Fix landed in helm/helm commit ba6c9a29efa7 — awaiting tagged release

https://github.com/helm/helm/commit/ba6c9a29efa7bf9198dad6a5ec12b4fb30c96017
github_pr

fix(engine): prevent Files.Lines panic on empty file

Fix merged in helm/helm PR #32290 on 2026-07-16 — awaiting tagged release

https://github.com/helm/helm/pull/32290
generic🟡 PoC Available

Helm Files.Lines panic on empty file causes deterministic render failure · Issue #32279 · helm/helm · GitHub

https://github.com/helm/helm/issues/32279

Vendor Advisories for CVE-2026-63308(5)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhathelm3-main-3.21.4-0.1.hum12026-08-15redhat
redhathelm4-main-4.2.3-0.1.2.hum12026-07-20redhat
redhathelm3-main-3.21.3-0.1.2.hum12026-07-20redhat

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.

Data Freshness Timeline

(refreshed 12× in last 7d / 79× 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 154 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-63308?
CVE-2026-63308 is a medium vulnerability published on July 17, 2026. Helm through 4.2.3, fixed in commit ba6c9a2, contains a denial of service vulnerability in the Files.Lines template helper in pkg/engine/files.go that allows attackers to trigger an index out of range panic by including zero-length byte slices in chart files. Attackers can include empty files in…
When was CVE-2026-63308 disclosed?
CVE-2026-63308 was first published in the National Vulnerability Database on July 17, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63308 actively exploited?
CVE-2026-63308 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 80.3% of all scored CVEs.
What is the CVSS score of CVE-2026-63308?
CVE-2026-63308 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-63308?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63308, 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-63308

Explore →

Is Your Infrastructure Affected by CVE-2026-63308?

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

Start Free Scan →Browse All CVEs