CVE-2026-65695: Office-Word-MCP-Server through 1

What it is

CVE-2026-65695, a CWE-22 path traversal in Office-Word-MCP-Server through 1.1.11, published 2026-07-23. The existing summary already carries the mechanism in full; what the page adds beyond it is the CVSS vector breakdown, the NVD status, and the fact that no fixed version is named.

Preconditions / Affected

The CVSS 4.0 vector is CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N (7.6 HIGH). Two components shape how you should weigh this against the raw score:

• UI:P (passive user interaction) and AC:H (high attack complexity) — this is not a fire-and-forget remote exploit. The attacker must influence the filename argument through the LLM-agent flow, and success depends on conditions outside their control.
• PR:N — no privileges required, and AV:N — network reachable. Confidentiality and integrity impact are both High (VC:H/VI:H); availability is None (VA:N), consistent with read/overwrite of .docx files rather than service disruption.

What to do

The page names no fixed version — the affected range is "through 1.1.11" with no patched release cited, and NVD status is Deferred. There is no vendor advisory link, only the researcher writeup (geo-chen/oss) and a VulnCheck advisory. Practically, treat this as unpatched: constrain the MCP server's working directory at the deployment layer and do not rely on check_file_writeable or ensure_docx_extension for confinement, since the page confirms neither does base-directory or realpath validation.

Caveats

Status "Deferred" means NVD is not actively reprioritizing this analysis; the score and vector stand but may not reflect later vendor input. No remediation, no proof-of-concept command, and no detection guidance appear on the page — the two reference links (not fetched here) are where any exploit detail or fix would live.