CVE-2026-61625 is a medium-severity (CVSS 6.8) Path Traversal vulnerability in github.com/VictoriaMetrics/VictoriaMetrics. O3 Security confirms whether CVE-2026-61625 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
VictoriaMetrics vmrestore: path traversal via crafted backup part names escapes restore root
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-61625.
Real-World Exposure
github.com/VictoriaMetrics/VictoriaMetrics🐹github.com/VictoriaMetrics/VictoriaMetrics🐹github.com/VictoriaMetrics/VictoriaMetricsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/VictoriaMetrics/VictoriaMetrics | ≥ 1.137.0&&< 1.146.0 | 1.146.0 |
| 🐹Go | github.com/VictoriaMetrics/VictoriaMetrics | ≥ 1.123.0&&< 1.136.12 | 1.136.12 |
| 🐹Go | github.com/VictoriaMetrics/VictoriaMetrics | all versions | 1.122.25 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/VictoriaMetrics/VictoriaMetrics. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/VictoriaMetrics/VictoriaMetrics to 1.146.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-61625 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-61625 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-61625. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-61625 in your dependencies?
O3 detects CVE-2026-61625 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.