CVE-2026-63308: Helm Files.Lines Denial of Service via Empty Chart Files
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.48% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No special conditions are required; it is repeatable.
- Fixed version: azl3 cert-manager 1.12.15-11 on Azure Linux 3.0 1.12.15-11.
Low priority for now. Upgrade to azl3 cert-manager 1.12.15-11 on Azure Linux 3.0 1.12.15-11 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 17, 2026
- Updated
- Oct 29, 2026
- EPSS
- 0.4% · 41th percentile
- CWE
- CWE-129
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · VulnCheck
- 5.3
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| helm | helm | cpe:2.3:a:helm:helm |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- helm helmup to 4.2.3 inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulnCheck). Independent of NVD's CPE analysis and usually ahead of it.
helm helm
- ba6c9a29efa7bf9198dad6a5ec12b4fb30c96017not affected
- up to and including 4.2.3affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| openSUSE:Leap 16.0 | helm | before 3.21.3-160000.2.1 | 3.21.3-160000.2.1 |
| openSUSE:Tumbleweed | helm | before 4.2.3-4.1 | 4.2.3-4.1 |
| openSUSE:Tumbleweed | helm3 | before 3.21.3-4.1 | 3.21.3-4.1 |
| Red Hat:hummingbird:1 | helm3 | before 0:3.21.3-0.1.2.hum1 | 0:3.21.3-0.1.2.hum1 |
| Red Hat:hummingbird:1 | helm3 | before 0:3.21.4-0.1.hum1 | 0:3.21.4-0.1.hum1 |
| Red Hat:hummingbird:1 | helm4 | before 0:4.2.3-0.1.2.hum1 | 0:4.2.3-0.1.2.hum1 |
| SUSE:Linux Enterprise Micro 5.5 | helm | before 3.21.3-150000.1.93.1 | 3.21.3-150000.1.93.1 |
| SUSE:Linux Micro 6.0 | helm | before 3.21.3-2.1 | 3.21.3-2.1 |
| SUSE:Linux Micro 6.1 | helm | before 3.21.3-slfo.1.1_2.1 | 3.21.3-slfo.1.1_2.1 |
| SUSE:Linux Micro 6.2 | c-ares | before 1.34.8-160000.1.1 | 1.34.8-160000.1.1 |
| SUSE:Linux Micro 6.2 | helm | before 3.21.3-160000.2.1 | 3.21.3-160000.2.1 |
Same product
helm: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-18658In Helm 2.x before 2.15.2, commands that deal with loading a chart as a directory or packaging a chart provide an opportunity for a maliciou40Plan
- CVE-2019-1010275helm Before 2.7.2 is affected by: CWE-295: Improper Certificate Validation.39Monitor
- CVE-2025-53547Helm Chart Dependency Updating With Malicious Chart.yaml Content And Symlink Can Lead To Code Execution34Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-35204Apr 9, 2026 · Helm has a path traversal in plugin metadata version enables arbitrary file write outside Helm plugin directory33Monitor
- ← EarlierCVE-2026-35205Apr 9, 2026 · Helm's plugin verification fails open when .prov is missing, allowing unsigned plugin install33Monitor
- ← EarlierCVE-2026-35206Apr 9, 2026 · Helm Chart extraction output directory collapse via `Chart.yaml` name dot-segment19Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| azl3 cert-manager 1.12.15-11 on Azure Linux 3.0 | 1.12.15-11 · CBL-Mariner Releases | Microsoft (MSRC) |
| opensuse:helm | 4.2.3-4.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:helm3 | 3.21.3-4.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:helm3 | 0:3.21.3-0.1.2.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:helm4 | 0:4.2.3-0.1.2.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| suse:c-ares | 1.34.8-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:helm | 3.21.3-2.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- George Chenfinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- P
- Scope
- X
Weakness class (CWE)
CWE-129 · Improper Validation of Array IndexCVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.