CVE-2026-61625 json
VictoriaMetrics vmrestore: path traversal via crafted backup part names escapes restore root
published 2mo ago modified 16d ago also GHSA-8q3c-rjr9-xxrp , GO-2026-6366 , EUVD-2026-63474
- cvss
- 6.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/VictoriaMetrics/VictoriaMetrics 1.122.25, 1.136.12, 1.146.0
- govulncheck-vulndb SLES 16.0, SLES for SAP applications 16.0 0.0.20260916T180043-160000.1.1
suse advisories SUSE-SU-2026:23855-1SUSE-SU-2026:23863-1
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260916T180043-160000.1.1
opensuse advisories openSUSE-SU-2026:21897-1
Is CVE-2026-61625 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2mo ago
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:N |
| GitHub | 3.1 | 6.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/VictoriaMetrics/VictoriaMetrics | >=1.137.0, <1.146.0 >=1.123.0, <1.136.12 <1.122.25 |
1.146.0 1.136.12 1.122.25 |
Affected products
- VictoriaMetrics VictoriaMetrics
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/VictoriaMetrics/VictoriaMetrics/commit/710c920d6083327042a309e449fae4383617d817
web, patch
-
github.com
/VictoriaMetrics/VictoriaMetrics/security/advisories/GHSA-8q3c-rjr9-xxrp
web, advisory
-
github.com
/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.122.25
web
-
github.com
/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.136.12
web
-
github.com
/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.146.0
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-61625
advisory
-
github.com
/VictoriaMetrics/VictoriaMetrics
package
Sources
- CVE List CVE-2026-61625
- GitHub Advisory GHSA-8q3c-rjr9-xxrp
- NVD CVE-2026-61625
- OSV GO-2026-6366
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.