GHSA-8Q3C-RJR9-XXRP

Vulnerability from github – Published: 2026-09-03 17:49 – Updated: 2026-09-03 17:49
VLAI
Summary
VictoriaMetrics vmrestore: Path traversal via crafted backup part names escapes restore root
Details

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

  • https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.146.0
  • https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.136.12
  • https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.122.25

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 when granting access to backup storage buckets.

Severity
6.8 (Medium)
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:N
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/VictoriaMetrics/VictoriaMetrics"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "1.137.0"
            },
            {
              "fixed": "1.146.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/VictoriaMetrics/VictoriaMetrics"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "1.123.0"
            },
            {
              "fixed": "1.136.12"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/VictoriaMetrics/VictoriaMetrics"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.122.25"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-61625"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-22"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-09-03T17:49:29Z",
    "nvd_published_at": "2026-08-20T17:18:51Z",
    "severity": "MODERATE"
  },
  "details": "### Summary\nThe 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.\n\n### Impact\nAn 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\u0027s filesystem permissions.\n\n### Patches\nVersions 1.146.0, 1.136.12, 1.122.25\n\n### Resources\n  - https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.146.0\n  - https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.136.12\n  - https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.122.25\n\n### Note\nVictoriaMetrics\u0027 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 when granting access to backup storage buckets.",
  "id": "GHSA-8q3c-rjr9-xxrp",
  "modified": "2026-09-03T17:49:29Z",
  "published": "2026-09-03T17:49:29Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/VictoriaMetrics/VictoriaMetrics/security/advisories/GHSA-8q3c-rjr9-xxrp"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-61625"
    },
    {
      "type": "WEB",
      "url": "https://github.com/VictoriaMetrics/VictoriaMetrics/commit/710c920d6083327042a309e449fae4383617d817"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/VictoriaMetrics/VictoriaMetrics"
    },
    {
      "type": "WEB",
      "url": "https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.122.25"
    },
    {
      "type": "WEB",
      "url": "https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.136.12"
    },
    {
      "type": "WEB",
      "url": "https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.146.0"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "VictoriaMetrics vmrestore: Path traversal via crafted backup part names escapes restore root"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.