<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 20 Nov 2026 16:54:19 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-409035</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-409035</link>
      <description>EUVD-2026-409035</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-409035</guid>
    </item>
    <item>
      <title>fkie_cve-2026-62964</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-62964</link>
      <description>&lt;p&gt;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&amp;#39;s repository-confinement invariant and can lead to arbitrary host code execution. This issue is fixed in version 0.55.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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&amp;#39;s repository-confinement invariant and can lead to arbitrary host code execution. This issue is fixed in version 0.55.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-62964</guid>
    </item>
    <item>
      <title>GHSA-w42c-h7hr-f67p — Gortex: Arbitrary file write / repo-confinement escape in `write_file` / `edit_file` / `move_inline` MCP tools → code e…</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-w42c-h7hr-f67p</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/zzet/gortex&lt;/p&gt;
&lt;p&gt;### Summary
Gortex is an MCP server exposing `write_file`, `edit_file`, and `move_inline` tools. `resolveFilePath` **exempts absolute paths** from confinement, and the write handlers — unlike `read_file` / `get_symbol_source` — **never call `guardSymlinkWithinRepo`**. A single MCP `write_file` call with an absolute path writes any file the daemon user can, **outside every indexed repo root** (`AtomicWriteFile`&amp;#39;s `MkdirAll` auto-creates missing parents). Writing `~/.zshrc`, `~/.bashrc`, `.git/hooks/pre-commit`, or a cron/systemd unit yields code execution on the next shell/commit. This directly violates the project&amp;#39;s own `SECURITY.md` invariant *&amp;#34;File-path resolution is **confined to indexed repository roots**&amp;#34;*&lt;/p&gt;
&lt;p&gt;### Affected
`internal/mcp/tools_fileops.go` (+ `tools_move_inline.go`), HEAD `28fa017` (v0.53.0).
**CWE-22** (Path Traversal) / **CWE-73** (External Control of File Name/Path) → **CWE-94** (code execution).&lt;/p&gt;
&lt;p&gt;### Vulnerable code
`internal/mcp/tools_fileops.go:54-62` `resolveFilePath` exempts absolute paths from the repo-root confinement; the write sink at `:793` (`AtomicWriteFile`, `write_file`) and `:676` (`edit_file`) run with **no** `guardSymlinkWithinRepo`. The asymmetry is the bug: `read_file` (`:940`) and `get_symbol_source` **do** call `guardSymlinkWithinRepo`; the write path does not.&lt;/p&gt;
&lt;p&gt;### PoC (executed)
The PoC (`internal/mcp/poc_arbitrary_write_test.go`, package `mcp`) builds the server via the repo&amp;#39;s **own** `newSingleRepoServer(t)` harness and invokes the…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/zzet/gortex&lt;/p&gt;
&lt;p&gt;### Summary
Gortex is an MCP server exposing `write_file`, `edit_file`, and `move_inline` tools. `resolveFilePath` **exempts absolute paths** from confinement, and the write handlers — unlike `read_file` / `get_symbol_source` — **never call `guardSymlinkWithinRepo`**. A single MCP `write_file` call with an absolute path writes any file the daemon user can, **outside every indexed repo root** (`AtomicWriteFile`&amp;#39;s `MkdirAll` auto-creates missing parents). Writing `~/.zshrc`, `~/.bashrc`, `.git/hooks/pre-commit`, or a cron/systemd unit yields code execution on the next shell/commit. This directly violates the project&amp;#39;s own `SECURITY.md` invariant *&amp;#34;File-path resolution is **confined to indexed repository roots**&amp;#34;*&lt;/p&gt;
&lt;p&gt;### Affected
`internal/mcp/tools_fileops.go` (+ `tools_move_inline.go`), HEAD `28fa017` (v0.53.0).
**CWE-22** (Path Traversal) / **CWE-73** (External Control of File Name/Path) → **CWE-94** (code execution).&lt;/p&gt;
&lt;p&gt;### Vulnerable code
`internal/mcp/tools_fileops.go:54-62` `resolveFilePath` exempts absolute paths from the repo-root confinement; the write sink at `:793` (`AtomicWriteFile`, `write_file`) and `:676` (`edit_file`) run with **no** `guardSymlinkWithinRepo`. The asymmetry is the bug: `read_file` (`:940`) and `get_symbol_source` **do** call `guardSymlinkWithinRepo`; the write path does not.&lt;/p&gt;
&lt;p&gt;### PoC (executed)
The PoC (`internal/mcp/poc_arbitrary_write_test.go`, package `mcp`) builds the server via the repo&amp;#39;s **own** `newSingleRepoServer(t)` harness and invokes the…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-w42c-h7hr-f67p</guid>
    </item>
  </channel>
</rss>
