Directory Traversal Affecting telegraf-1.39 package, versions <1.39.3-r9
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CHAINGUARDLATEST-TELEGRAF139-19706374
- published12 Sept 2026
- disclosed10 Sept 2026
Introduced: 10 Sep 2026
NewCVE-2026-88014 (opens in a new tab)How to fix?
Upgrade Chainguard telegraf-1.39 to version 1.39.3-r9 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream telegraf-1.39 package and not the telegraf-1.39 package as distributed by Chainguard.
See How to fix? for Chainguard relevant fixed versions and status.
rclone is a command-line program to sync files and directories to and from different cloud storage providers. From 1.72.0 until 1.75.1, the archive ZIP backend method (*Fs).readZip in backend/archive/zip/zip.go accepts archive/zip.File.Name values from an untrusted central directory and exposes cleaned entry names without ensuring that they remain inside the archive namespace. Entries such as ../../etc/cron.d/evil can survive path.Clean and become Object.Remote() values that fs/sync and fs/operations use as destination-relative paths, allowing rclone copy or sync to write outside the selected destination on backends that do not independently confine the path. The non-empty root check also used strings.HasPrefix without a path boundary, so root foo could incorrectly include sibling foobar entries. This issue is fixed in version 1.75.1.