CVE-2026-61625

MEDIUMPre-NVD 6.86.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (32nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
6.8EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
6.8
EG Score
6.8MEDIUMmedium confidence
EG Risk
31
EG Risk 31/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity68% × 45%
The EG Score, 6.8 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 20, 2026

Last Modified

September 18, 2026

Advisory Details (5)

Auto-updated Aug 20, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

v1.146.0

Patch available: VictoriaMetrics/VictoriaMetrics v1.146.0

https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.146.0
GitHub release Patch Available

v1.136.12

Patch available: VictoriaMetrics/VictoriaMetrics v1.136.12

https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.136.12
GitHub release Patch Available

v1.122.25

Patch available: VictoriaMetrics/VictoriaMetrics v1.122.25

https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.122.25
GitHub commit

commit 710c920d6083 (VictoriaMetrics/VictoriaMetrics)

Fix landed in VictoriaMetrics/VictoriaMetrics commit 710c920d6083 — awaiting tagged release

https://github.com/VictoriaMetrics/VictoriaMetrics/commit/710c920d6083327042a309e449fae4383617d817
GitHub advisoryMentions a patch (unverified)

vmrestore: path traversal via crafted backup part names escapes restore root · Advisory · VictoriaMetrics/VictoriaMetrics · GitHub

https://github.com/VictoriaMetrics/VictoriaMetrics/security/advisories/GHSA-8q3c-rjr9-xxrp

Vendor Advisories for CVE-2026-61625(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/VictoriaMetrics/VictoriaMetrics—
  • 1.137.0 up to 1.146.0: fixed in 1.146.0
  • 1.123.0 up to 1.136.12: fixed in 1.136.12
  • every version up to 1.122.25: fixed in 1.122.25
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 46× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  3. 2026-10-12 15:50 UTCEG score recompute
  4. 2026-10-11 19:34 UTCEG score recompute
  5. 2026-10-11 16:49 UTCEG score recompute
  6. 2026-10-11 14:11 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  10. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  11. 2026-10-08 05:33 UTCEG score recompute
  12. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  13. 2026-10-07 06:42 UTCEG score recompute
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  15. 2026-10-06 07:52 UTCEG score recompute
  16. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  17. 2026-10-05 05:00 UTCEG score recompute
  18. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  19. 2026-10-04 04:30 UTCEG score recompute
  20. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  21. 2026-10-03 05:39 UTCEG score recompute
  22. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  23. 2026-10-02 06:49 UTCEG score recompute
  24. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  25. 2026-10-01 07:04 UTCEG score recompute
Show 64 more
  1. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  2. 2026-09-30 08:14 UTCEG score recompute
  3. 2026-09-29 01:56 UTCEG score recompute
  4. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  5. 2026-09-28 02:00 UTCEG score recompute
  6. 2026-09-27 03:03 UTCEG score recompute
  7. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  8. 2026-09-24 19:08 UTCEG score recompute
  9. 2026-09-23 20:05 UTCEG score recompute
  10. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  11. 2026-09-22 19:45 UTCEG score recompute
  12. 2026-09-21 17:54 UTCEG score recompute
  13. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  14. 2026-09-19 19:26 UTCEG score recompute
  15. 2026-09-18 20:20 UTCEG score recompute
  16. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  17. 2026-09-17 21:19 UTCEG score recompute
  18. 2026-09-16 20:02 UTCEG score recompute
  19. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  20. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  21. 2026-09-15 18:49 UTCEG score recompute
  22. 2026-09-13 21:08 UTCEG score recompute
  23. 2026-09-12 22:18 UTCEG score recompute
  24. 2026-09-11 23:28 UTCEG score recompute
  25. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  26. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  27. 2026-09-11 00:18 UTCEG score recompute
  28. 2026-09-09 01:57 UTCEG score recompute
  29. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  30. 2026-09-07 21:27 UTCEG score recompute
  31. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  32. 2026-09-06 22:37 UTCEG score recompute
  33. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  34. 2026-09-05 23:47 UTCEG score recompute
  35. 2026-09-05 00:58 UTCEG score recompute
  36. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  37. 2026-09-03 03:14 UTCEG score recompute
  38. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  39. 2026-09-02 04:20 UTCEG score recompute
  40. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  41. 2026-09-01 05:30 UTCEG score recompute
  42. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  43. 2026-08-31 06:33 UTCEG score recompute
  44. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  45. 2026-08-30 07:44 UTCEG score recompute
  46. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  47. 2026-08-29 08:54 UTCEG score recompute
  48. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  49. 2026-08-28 10:04 UTCEG score recompute
  50. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  51. 2026-08-27 11:14 UTCEG score recompute
  52. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  53. 2026-08-26 12:24 UTCEG score recompute
  54. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  55. 2026-08-24 14:39 UTCEG score recompute
  56. 2026-08-23 15:47 UTCEG score recompute
  57. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  58. 2026-08-22 16:58 UTCEG score recompute
  59. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  60. 2026-08-20 19:18 UTCEG score recompute
  61. 2026-08-20 18:32 UTCEG score recompute
  62. 2026-08-20 17:33 UTCEG score recompute
  63. 2026-08-20 16:52 UTCEG score recomputeFirst assessed: 6.8 MEDIUM
  64. 2026-08-20 16:51 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Same product

1 shown

Go:github.com/VictoriaMetrics/VictoriaMetrics

Frequently asked(5)

What is CVE-2026-61625?
CVE-2026-61625 is a medium-severity vulnerability; its CVE record was published on August 20, 2026. 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…
When was the CVE record for CVE-2026-61625 published?
The CVE record for CVE-2026-61625 was published on August 20, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 18, 2026; the record at its source may have been updated since.
Is CVE-2026-61625 actively exploited?
CVE-2026-61625 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61625?
CVE-2026-61625 has a CVSS base score of 6.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61625?
A fix for CVE-2026-61625 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-61625 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-61625

Explore →

Is Your Infrastructure Affected by CVE-2026-61625?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs