VictoriaMetrics vmrestore: Path traversal via crafted backup part names escapes restore root

CVE-2026-61625 · Published Sep 3, 2026 · updated Sep 15, 2026

Medium6.8

Fix: upgrade to 1.122.25 or later (3 fixed versions below)

Summary

The VictoriaMetrics vmrestore utility does not validate backup part path components before writing restored files to the local filesystem. An attacker who can provide or modify a backup source can craft object names containing .. path components that cause vmrestore to write files outside the intended -storageDataPath restore root, subject to the permissions of the vmrestore process.

Impact

An attacker who can supply or modify the backup source -- for example by writing malicious object names to a compromised or misconfigured storage bucket -- can cause arbitrary files to be created or overwritten on the host running vmrestore, within the limits of the process's filesystem permissions.

Patches

Versions 1.146.0, 1.136.12, 1.122.25

Resources

https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.146.0
https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.136.12
https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.122.25

Note

VictoriaMetrics' security model assumes backup sources are trusted and access-controlled. This vulnerability requires an attacker to have write access to the backup storage (e.g. S3, GCS, or Azure Blob Storage bucket) used as the -src for vmrestore. Under a correctly secured deployment where backup storage access is properly restricted, unauthorized exploitation...

Affected versions

Package	Affected	Fixed in
github.com/VictoriaMetrics/VictoriaMetrics Go	>= 1.137.0, < 1.146.0	1.146.0
	>= 1.123.0, < 1.136.12	1.136.12
	< 1.122.25	1.122.25

Details and references

### Summary The VictoriaMetrics `vmrestore` utility does not validate backup part path components before writing restored files to the local filesystem. An attacker who can provide or modify a backup source can craft object names containing `..` path components that cause vmrestore to write files outside the intended `-storageDataPath` restore root, subject to the permissions of the `vmrestore` process. ### Impact An attacker who can supply or modify the backup source -- for example by writing malicious object names to a compromised or misconfigured storage bucket -- can cause arbitrary files to be created or overwritten on the host running `vmrestore`, within the limits of the process's filesystem permissions. ### Patches Versions 1.146.0, 1.136.12, 1.122.25 ### Resources - https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.146.0 - https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.136.12 - https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.122.25 ### Note VictoriaMetrics' security model assumes backup sources are trusted and access-controlled. This vulnerability requires an attacker to have write access to the backup storage (e.g. S3, GCS, or Azure Blob Storage bucket) used as the `-src` for `vmrestore`. Under a correctly secured deployment where backup storage access is properly restricted, unauthorized exploitation of this issue should not be possible. Users are advised to follow the principle of least privilege when granting access to backup storage buckets.

CVSS 3.1: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:N
Severity from: GitHub (reviewed advisory)
Weakness: CWE-22
Also known as: CVE-2026-61625, GO-2026-6366

More VictoriaMetrics advisories

All VictoriaMetrics

Low 2.7Nov 25, 2025

VictoriaMetrics' Snappy Decoder DoS Vulnerability is Causing OOMCVE-2025-65942fixed in 1.110.23 +2