> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/release-notes/developer-tools/commander/commander-18.1.7.md).

# Commander 18.1.7

Released on Oct 7, 2026

### Security

* **KC-1471:** Prevent newline injection in `connect` command prompts. Control characters are now escaped and shell comments handled, closing a path where an operator with Can Edit on a shared record could hide commands in a confirmation prompt and exfiltrate device credentials without being noticed.
* **KC-1462:** Validate record ownership in the `audit-log` command. Only operator-owned records are now eligible as an export destination, preventing an attacker from hijacking an export by sharing a malicious record with a matching title. Also removes TLS verification bypass from Splunk exports.

### Features

* **KC-1442:** Add Classic-to-NSF conversion command, with negative-flow tests and support for skipping records that are already nested-share.
* **DR-1324:** Generate and deliver tokens.

### Improvements

* **KC-1461:** Limit NSF folder depth on import, with a sibling-flatten fallback and a structure report when limits are exceeded.
* Improve `LoadRecordTypes` command: continues past invalid custom record types instead of aborting, with more verbose and color-coded logging.
* Add filtering while printing inherited and denied-access permissions for folders and records.

### Fixes

* Fix folder properties mutation bug in the NSF `share-folder` command.
* Fix service mode response status.
* Fix SaaS field check incorrectly flagging non-required blank values.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.keeper.io/release-notes/developer-tools/commander/commander-18.1.7.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.