CVE-2026-63308

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreHIGH confidence

Score 4.3 from GitHub Security Advisory published 2026-07-17. a secondary CVSS source baseline 4.3; sources differ by 0.0.

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

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

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
4.3
EG Score
4.3(high)
EG Risk
35(Track)
EG Risk 35/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
Severity43% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
14.4%
KEV
Not listed

Published

July 17, 2026

Last Modified

July 17, 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(2)

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 12× in last 7d / 16× 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-24 14:18 UTCEPSS rescore
  2. 2026-07-24 14:18 UTCEPSS rescore
  3. 2026-07-23 14:18 UTCEPSS rescore
  4. 2026-07-23 14:18 UTCEPSS rescore
  5. 2026-07-23 03:22 UTCEG score recompute
  6. 2026-07-22 14:08 UTCEPSS rescore
  7. 2026-07-22 14:08 UTCEPSS rescore
  8. 2026-07-21 15:25 UTCEPSS rescore
  9. 2026-07-21 15:25 UTCEPSS rescore
  10. 2026-07-20 17:08 UTCEPSS rescore
  11. 2026-07-19 14:31 UTCEPSS rescore
  12. 2026-07-19 02:29 UTCEPSS rescore
  13. 2026-07-17 18:31 UTCEG score recompute
  14. 2026-07-17 18:31 UTCGHSA enrichment
  15. 2026-07-17 16:20 UTCEG score recompute
  16. 2026-07-17 16:19 UTCMITRE cvelistV5first tracked

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. 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 14.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-63308?
CVE-2026-63308 has a CVSS v3 base score of 4.3 (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