cve.bz

CVE-2026-61625 victoriametrics victoriametrics: Path traversal

6.8 mediumEPSS 0.4%Fix available

Medium (6.8) in victoriametrics victoriametrics. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/VictoriaMetrics/VictoriaMetrics 1.122.25, 1.136.12, 1.146.0.

On this page
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.

Severity

CVSS 3.1

6.8 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 35th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-61625 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-61625?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-61625?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-61625 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
VictoriaMetrics>= 1.137.0, < 1.146.0
VictoriaMetrics>= 1.123.0, < 1.136.12
VictoriaMetrics< 1.122.25

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-8q3c-rjr9-xxrpGogithub.com/VictoriaMetrics/VictoriaMetrics>=1.137.0 <1.146.01.146.0
GHSA-8q3c-rjr9-xxrpGogithub.com/VictoriaMetrics/VictoriaMetrics>=1.123.0 <1.136.121.136.12
GHSA-8q3c-rjr9-xxrpGogithub.com/VictoriaMetrics/VictoriaMetrics<1.122.251.122.25
GO-2026-6366Gogithub.com/VictoriaMetrics/VictoriaMetrics<1.122.25
>=1.123.0 <1.136.12
>=1.137.0 <1.146.0
1.122.25, 1.136.12, 1.146.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0govulncheck-vulndb0.0.20260916T180043-160000.1.1SUSE-SU-2026:23855-1 SUSE-SU-2026:23863-1
openSUSELeap 16.0govulncheck-vulndb0.0.20260916T180043-160000.1.1openSUSE-SU-2026:21897-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE · openSUSE.

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON