Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-61625 medium CVSS 6.8

Path Traversal in github.com/VictoriaMetrics/VictoriaMetrics (CVE-2026-61625)

Summary

Path traversal in github.com/VictoriaMetrics/VictoriaMetrics (CVE-2026-61625). Data can be tampered with by attackers. Exploitable via vmrestore. Mitigation: upgrade to 1.122.25 or later.

Original description

The description as published by the source.

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

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 wh…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-61625 has been found in github.com/VictoriaMetrics/VictoriaMetrics.
Attackers can target a specific entry point like vmrestore over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.8/10.
What to do: upgrade github.com/VictoriaMetrics/VictoriaMetrics to 1.122.25 or later.
If unsure, ask your IT team or search "github.com/VictoriaMetrics/VictoriaMetrics CVE-2026-61625" on the vendor's site.

CVE-2026-61625 (github.com/VictoriaMetrics/VictoriaMetrics) — CWE-22 / CVSS v3 6.8
Attack vector: remote (network-reachable)
Attack surface: vmrestore
Patched: 1.122.25 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Path traversal (CWE-22) exists in github.com/VictoriaMetrics/VictoriaMetrics. Attackers reach the vulnerable code path via vmrestore.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/VictoriaMetrics/VictoriaMetrics. Attack surface: vmrestore.

🔥 Severity

Severity: Medium (CVSS 6.8/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 1.122.25.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/VictoriaMetrics/VictoriaMetrics' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/VictoriaMetrics/VictoriaMetrics' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/VictoriaMetrics/VictoriaMetrics を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/VictoriaMetrics/VictoriaMetrics to 1.122.25

    ステージング環境で 1.122.25 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/VictoriaMetrics/VictoriaMetrics
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.122.25"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details