CVE
Gortex arbitrary file write in MCP write_file and edit_file tools
- Exploited
- No known exploitation
- Fix
- Fixed in 0.55.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.55.0.
Summary
Gortex's file-writing tools (write_file, edit_file, and move_inline) can be abused by a local attacker with no login to create or overwrite files anywhere the Gortex daemon user can access, which can lead to arbitrary code execution. Exploitation requires some user interaction.
Original description
Gortex is a high-performance code-intelligence engine for AI agents and integrated development environments. Prior to 0.55.0, resolveFilePath in internal/mcp/tools_fileops.go accepts absolute paths without checking indexed repository roots, while write_file, edit_file, and move_inline in internal/mcp/tools_move_inline.go omit guardSymlinkWithinRepo before reaching AtomicWriteFile and related write sinks. A caller that can influence MCP tool arguments can therefore create or overwrite files anywhere the daemon user can access, including startup or hook files that execute code on a later trigger. The flaw violates Gortex's repository-confinement invariant and can lead to arbitrary host code execution. This issue is fixed in version 0.55.0.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.8/10CVSS 7.8
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 30 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 0.55.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-62964 (Gortex: Arbitrary file write / repo-confinement escape in `write_file` / `edit_file` / `move_inline` MCP tools → code execution), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-62964 (entry last updated 2026-11-18):
Affected:
- zzet gortex: fixed in 0.55.0
Fixed versions: 0.55.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-62964 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-62964 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/zzet/gortex/security/advisories/GHSA-w42c-h7hr-f67p
- https://github.com/zzet/gortex/commit/5ba2f066dd6dcd726c4e61b74851862dc596d994
- https://github.com/zzet/gortex/releases/tag/v0.55.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-62964
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-62964"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- zzet gortex
fixed in 0.55.0
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · zzet/gortex · Advisory GHSA-w42c-h7hr-f67p |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-62964 |
| Record | NVD · CVE-2026-62964 |
| Other links 2 | |
| Repository | GitHub · zzet/gortex · Commit 5ba2f066 |
| Repository | GitHub · zzet/gortex · Release v0.55.0 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-62964
Is CVE-2026-62964 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-62964?
gortex: before 0.55.0.Source: cve.now feed data
How do I fix CVE-2026-62964?
Upgrade to a fixed version: 0.55.0.Source: cve.now feed data