CVE-2024-25620VulnerabilityPublished 5 Dec 2024Updated 18 Oct 2026

SUSE · Recommended update for helm

Affects SUSESource GCVE Database

Not known to be exploited : upgrade to 4.15.3 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.15.3

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Dec 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade SUSE to 4.15.3.

Affected software

Product	Affected	Fixed in
SUSE Product Security Team SUSE	Affected >=4.15.0 <4.15.3 =3.16.3 SUSE aarch64 helm-0:3.16.3-150000.1.38.1.aarch64 noarch helm-bash-completion-0:3.16.3-150000.1.38.1.noarch	Fixed in 4.15.3

AI-suggested

A fix is available. Users should upgrade Helm to version 3.14.1 or later. For Red Hat OpenShift Container Platform 4.15 users, upgrade to version 4.15.3 or later, which includes updated container images addressing this vulnerability. Follow vendor-provided upgrade instructions for OpenShift clusters using the OpenShift CLI or web console. No additional mitigation steps are indicated by the vendor advisory.

Description

A path traversal vulnerability (CVE-2024-25620) was discovered in Helm's dependency management component. This vulnerability could allow improper handling of file paths, potentially leading to unauthorized file access or manipulation during dependency management operations. The issue has been addressed in Helm versions 3.14.1 and later, as well as in Red Hat OpenShift Container Platform 4.15.3 images. Users of affected versions are advised to upgrade to these fixed releases to mitigate the risk.

Impact

The vulnerability could allow an attacker to exploit path traversal in Helm's dependency management, potentially leading to unauthorized file access or modification during dependency resolution. This could impact the integrity and security of deployments using affected Helm versions or OpenShift Container Platform 4.15 images. No known exploits in the wild have been reported. The severity is assessed as medium/moderate by the vendor.

Summary

CVE-2024-25620 is a path traversal vulnerability in Helm's dependency management functionality. It involves improper handling of file paths that could be exploited to traverse directories outside the intended scope. The vulnerability was fixed in Helm version 3.14.1 and later. Red Hat OpenShift Container Platform 4.15.3 includes updated container images that address this issue. The Red Hat advisory rates this vulnerability as moderate severity and recommends upgrading affected OpenShift Container Platform 4.15 deployments to the updated packages and images. The vulnerability is tracked under CWE-22 (Improper Limitation of a Pathname to a Restricted Directory).

CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #6OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.1 (opens in a new tab)
Attack patterns
Path Traversal (opens in a new tab)
Using Slashes and URL Encoding Combined to Bypass Validation Logic (opens in a new tab)
Manipulating Web Input to File System Calls (opens in a new tab)
Using Escaped Slashes in Alternate Encoding (opens in a new tab)
Using Slashes in Alternate Encoding (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Oct 2026, 22:10 UTC

WeaknessesCWE-22

Technical details

References

Community reviews

Related threats