AIDEFEND in Action AIA-0130 Validated Research

Filesystem MCP: Symlink Races Escape Read and Move Boundaries

Two Filesystem MCP disclosures show a local process replacing a directory with a symlink after validation. One route reads an outside file by reopening its pathname; another moves an outside file into an allowed directory before reading it. The attacker needs local directory-mutation capability and tool calls, while the server must possess the required filesystem access. Version 2.3.0 is the announced repair.

Permission BypassPrivacy LeakageRuntime IsolationMCP Security
3 applicable AIDEFEND defenses
Source: Filesystem MCP read and same-device move race advisories 
Author: Model Context Protocol maintainers
Original article: Nov 11, 2026

Threat Analysis

  • The checked name can change: The read route resolves a permitted path, then opens it by name again. A local directory swap in that interval redirects the second lookup. The two-user Linux reproduction verifies that the server returns data the caller cannot directly read.
  • Move is a separate path: Same-device rename protects the destination but not the source parent. The demonstrated POSIX effect imports an outside file, then reads it inside the allowed tree. It also removes the original directory entry. This is distinct from exporting a file to an outside destination.
  • Prerequisites matter: The attacker must mutate local directories and trigger tool calls; the server needs the relevant file access. The detailed reproductions and announced affected ranges are different kinds of evidence. Neither proves exploitation against a customer deployment. Supporting primary records: separate move-path advisory.

Applicable AIDEFEND Defenses (3)

AID-H-003.010
Deployed AI Software Vulnerability Remediation Lifecycle
Very High
Deploy the announced 2.3.0 repair or a supported release containing both fixes, and inspect the package actually launched by every client. Test ordinary reads, head/tail, same-device moves and legitimate cross-device behavior independently with synthetic files. A monorepo tag is not the npm package version.
AID-H-018.009
Model-Callable Filesystem Path Confinement
Very High
For a maintained filesystem adapter, open from a trusted root and consume bytes only through the verified descriptor or handle. Do not validate realpath and then reopen the name. Integrate the platform-specific broker into all read variants, enforce the protected-root permission invariant and fail closed when object identity or required OS support cannot be verified. Protect both source and destination identities for rename, with separate operation permissions and descriptor-relative mutation. The Framework’s Linux reference additionally requires a broker-exclusive mutation tree; if that invariant cannot be enforced, disable that mutation profile. Preserve an indeterminate result after a successful rename followed by failed readback instead of blindly retrying. Review the complete adapter and operation population, then independently observe the exact file opened or moved. Include read/head/tail, same-device rename, cross-device paths and direct in-process entry points for every claimed platform. Count missing receipts or unsupported profiles as incomplete evidence, not a successful confinement test.
AID-I-001.001
Container-Based Isolation
Medium
Operators able to containerize the server can expose only the required working tree under a dedicated non-root identity, drop capabilities and omit home directories, host sockets and unrelated secret mounts. Verify the actual process UID and mount view. This removes many outside files from the server’s reach but does not repair a race involving files still accessible inside that boundary.

What Defenders Should Do Now

  • Update the actual launched package to 2.3.0 or a supported fixed release. Include read, head/tail and same-device move regression fixtures using synthetic files and separate OS identities.
  • Bind read access to the opened object and rename to both protected parents. Use platform-native descriptors or handles and verify object identity independently; string-prefix or realpath checks alone cannot close the race.
  • Reduce ambient filesystem authority with a dedicated identity and restricted mounts. Prevent untrusted mutation of a broker-owned root where that is the chosen guarantee, and disable unsupported mutation profiles.

Conclusion

AIDEFEND  ties this case to verified patch rollout, object-bound filesystem confinement and container-level reduction of accessible files. The central question is which object the operating system actually used, not whether the requested path once looked safe.

Last updated: