CVE-2026-77621: vectordotdev vector · Path Traversal
Affects vectordotdev vectorSource CVE Database V5
Not known to be exploited · CVSS 9.3 Critical : upgrade to 0.57.0 as a priority.
Data as of 5 Nov 2026, 23:24 UTC
- EPSS
- 1.1% chance of exploitation in 30 days – higher than 66% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.57.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:HExploitation evidence
Disclosed: evidence found.
CVE published 22 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade vector and vectordotdev/vector to 0.57.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| vectordotdevvector | Affected
| Fixed in
|
GitHubvectordotdev/vectorpkg:github/vectordotdev/vectorOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Vector to version 0.57.0 or later where this vulnerability is fixed. Until then, avoid processing untrusted event fields in file sink path templates or restrict event sources to trusted inputs.
Description
Vector is a high-performance observability data pipeline. From 0.10.0 until 0.57.0, the file sink renders its templated path from event fields and opens the result without confining it to an intended directory. When an untrusted source supplies an event field used by the path template, the value can contain an absolute path or parent-directory traversal, causing Vector to create parent directories and create or overwrite files outside the intended location with the Vector process privileges. The resulting file write can modify sensitive files and can lead to code execution when a scheduled task, authorization file, or subsequently executed script is targeted. This issue is fixed in version 0.57.0.
References
- github.com/vectordotdev/vector/security/advisories/GHSA-6342-xwvw-c637 (opens in a new tab)
- github.com/vectordotdev/vector/pull/25820 (opens in a new tab)
- github.com/vectordotdev/vector/pull/25830 (opens in a new tab)
- github.com/vectordotdev/vector/commit/6951064ed1d295fbff67a5ba7da5971fc6f58c46 (opens in a new tab)
- github.com/vectordotdev/vector/commit/8832452f57afb536ea0de53a093f9fd1b669ccec (opens in a new tab)
- github.com/vectordotdev/vector/releases/tag/v0.57.0 (opens in a new tab)