Homepage

Directory Traversal Affecting victoriatraces package, versions <0.9.4-r0

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.41% (32nd percentile)

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-MINIMOSLATEST-VICTORIATRACES-19537053
  • published5 Sept 2026
  • disclosed20 Aug 2026
Report a new vulnerability Found a mistake?

Introduced: 20 Aug 2026

CVE-2026-61625  (opens in a new tab)
CWE-22  (opens in a new tab)

How to fix?

Upgrade Minimos:latest victoriatraces to version 0.9.4-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream victoriatraces package and not the victoriatraces package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

VictoriaMetrics is a scalable solution for monitoring and managing time series data. Prior to 1.122.25, 1.136.12, and 1.146.0, vmrestore does not validate backup part path components before using lib/backup/actions/restore.go and lib/backup/fslocal/fslocal.go to write restored data below storageDataPath. An attacker who can supply or modify an S3, GCS, Azure Blob Storage, or other backup source can place .. components in object names. When an operator restores that source, the crafted names can create or overwrite files outside the intended restore root within the filesystem permissions of the vmrestore process. This issue is fixed in versions 1.122.25, 1.136.12, and 1.146.0.