VictoriaMetrics up to 1.122.24/1.136.11/1.145.x Restore restore.go path traversal

Summaryinfo

A vulnerability was found in VictoriaMetrics up to 1.122.24/1.136.11/1.145.x. It has been rated as problematic. The impacted element is an unknown function of the file lib/backup/actions/restore.go of the component Restore. The manipulation leads to path traversal. This vulnerability is referenced as CVE-2026-61625. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in VictoriaMetrics up to 1.122.24/1.136.11/1.145.x. It has been rated as problematic. This issue affects an unknown function of the file lib/backup/actions/restore.go of the component Restore. The manipulation with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. 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. Impacted is integrity. The summary by CVE is:

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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-61625 since 07/10/2026. The exploitation is known to be easy. The attack may be initiated remotely. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1006 for this issue.

Upgrading to version 1.122.25, 1.136.12 or 1.146.0 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• VictoriaMetrics

Version

• 1.122.0
• 1.122.1
• 1.122.2
• 1.122.3
• 1.122.4
• 1.122.5
• 1.122.6
• 1.122.7
• 1.122.8
• 1.122.9
• 1.122.10
• 1.122.11
• 1.122.12
• 1.122.13
• 1.122.14
• 1.122.15
• 1.122.16
• 1.122.17
• 1.122.18
• 1.122.19
• 1.122.20
• 1.122.21
• 1.122.22
• 1.122.23
• 1.122.24
• 1.136.0
• 1.136.1
• 1.136.2
• 1.136.3
• 1.136.4
• 1.136.5
• 1.136.6
• 1.136.7
• 1.136.8
• 1.136.9
• 1.136.10
• 1.136.11
• 1.145

Website

• Product: https://github.com/VictoriaMetrics/VictoriaMetrics/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion