https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 21:30:19 +0000 https://vulnerability.circl.lu/vuln/cleanstart-2026-pp41562 <p><strong>Affected:</strong> CleanStart: victoriametrics-operator</p> <p>Security vulnerability affects the victoriametrics-operator package. This issue is resolved in later releases. See references for vulnerability details.</p> <p><strong>Affected:</strong> CleanStart: victoriametrics-operator</p> <p>Security vulnerability affects the victoriametrics-operator package. This issue is resolved in later releases. See references for vulnerability details.</p> https://vulnerability.circl.lu/vuln/cleanstart-2026-pp41562 https://vulnerability.circl.lu/vuln/fkie_cve-2026-61625 <p>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.</p> <p>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.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-61625 https://vulnerability.circl.lu/vuln/ghsa-8q3c-rjr9-xxrp <p><strong>Affected:</strong> Go: github.com/VictoriaMetrics/VictoriaMetrics</p> <p>### 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.</p> <p>### 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&#39;s filesystem permissions.</p> <p>### Patches Versions 1.146.0, 1.136.12, 1.122.25</p> <p>### 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</p> <p>### Note VictoriaMetrics&#39; 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 w…</p> <p><strong>Affected:</strong> Go: github.com/VictoriaMetrics/VictoriaMetrics</p> <p>### 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.</p> <p>### 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&#39;s filesystem permissions.</p> <p>### Patches Versions 1.146.0, 1.136.12, 1.122.25</p> <p>### 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</p> <p>### Note VictoriaMetrics&#39; 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 w…</p> https://vulnerability.circl.lu/vuln/ghsa-8q3c-rjr9-xxrp