https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 17 Oct 2026 10:49:31 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-274873 EUVD-2026-274873 https://cve.radiocsirt.org/vuln/euvd-2026-274873 https://cve.radiocsirt.org/vuln/fkie_cve-2026-29064 <p>Zarf is an Airgap Native Packager Manager for Kubernetes. From version 0.54.0 to before version 0.73.1, a path traversal vulnerability in archive extraction allows a specifically crafted Zarf package to create symlinks pointing outside the destination directory, enabling arbitrary file read or write on the system processing the package. This issue has been patched in version 0.73.1.</p> <p>Zarf is an Airgap Native Packager Manager for Kubernetes. From version 0.54.0 to before version 0.73.1, a path traversal vulnerability in archive extraction allows a specifically crafted Zarf package to create symlinks pointing outside the destination directory, enabling arbitrary file read or write on the system processing the package. This issue has been patched in version 0.73.1.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-29064 https://cve.radiocsirt.org/vuln/ghsa-hcm4-6hpj-vghm <p><strong>Affected:</strong> Go: github.com/zarf-dev/zarf/src/pkg/archive</p> <p>### Summary</p> <p>A path traversal vulnerability in archive extraction allows a specifically crafted Zarf package to create symlinks pointing outside the destination directory, enabling arbitrary file read or write on the system processing the package.</p> <p>### What users should do Upgrade immediately to version v0.73.1</p> <p>If developers cannot upgrade immediately, only process Zarf packages from fully trusted sources until the fix is applied.</p> <p>If using trusted packages and archives - the only impact to this is updating zarf binary or SDK package versions. Previously created packages do not need to be rebuilt.</p> <p>### Who is affected</p> <p>- Any user of affected Zarf versions who processes packages from untrusted or semi-trusted sources. This includes packages received via file transfer, downloaded from registries, or shared across organizational boundaries. This includes use of the `zarf tools archiver decompress` functionality on generic archives.</p> <p>- Any SDK consumers of Zarf for the affected versions who utilize package load or archive operations.</p> <p>### What is the risk</p> <p>A malicious Zarf package or archive could create symlinks pointing to arbitrary locations on the filesystem. This could lead to unauthorized file reads, file overwrites, or in some scenarios, code execution on the system performing the extraction in the event a file on the system is both overwritten and executed. This vulnerability does not introduce an execution path explicitly.</p> <p>### Mitigating Factors</p> <p>If developers only p…</p> <p><strong>Affected:</strong> Go: github.com/zarf-dev/zarf/src/pkg/archive</p> <p>### Summary</p> <p>A path traversal vulnerability in archive extraction allows a specifically crafted Zarf package to create symlinks pointing outside the destination directory, enabling arbitrary file read or write on the system processing the package.</p> <p>### What users should do Upgrade immediately to version v0.73.1</p> <p>If developers cannot upgrade immediately, only process Zarf packages from fully trusted sources until the fix is applied.</p> <p>If using trusted packages and archives - the only impact to this is updating zarf binary or SDK package versions. Previously created packages do not need to be rebuilt.</p> <p>### Who is affected</p> <p>- Any user of affected Zarf versions who processes packages from untrusted or semi-trusted sources. This includes packages received via file transfer, downloaded from registries, or shared across organizational boundaries. This includes use of the `zarf tools archiver decompress` functionality on generic archives.</p> <p>- Any SDK consumers of Zarf for the affected versions who utilize package load or archive operations.</p> <p>### What is the risk</p> <p>A malicious Zarf package or archive could create symlinks pointing to arbitrary locations on the filesystem. This could lead to unauthorized file reads, file overwrites, or in some scenarios, code execution on the system performing the extraction in the event a file on the system is both overwritten and executed. This vulnerability does not introduce an execution path explicitly.</p> <p>### Mitigating Factors</p> <p>If developers only p…</p> https://cve.radiocsirt.org/vuln/ghsa-hcm4-6hpj-vghm