KIMI-1: Kimi Code did not enforce the permission rules in its own config (fixed in 2.6.0)

Short version. Kimi Code loaded the [[permission.rules]] in ~/.kimi-code/config.toml but did not enforce them in the runs we tested. Deny rules on shell commands, file reads and file writes did nothing in versions 2.1.1 to 2.5.2. Moonshot fixed this in 2.6.0, released on 12 November 2026. If you use Kimi Code, upgrade to 2.6.0 or later.

Others reported it too. Related behaviour was reported publicly by other users: MoonshotAI/kimi-code#2070 on 22 July 2026 (interactive sessions, 0.28.1) and #4420 and #4437 on 26 October 2026 (print mode, 2.3.x). We reported our findings privately to Moonshot on 9 October 2026 and again as a GitHub security advisory on 8 November.

What happened. With deny rules set for the shell, file reads and file writes, Kimi Code still ran the denied actions. Ask rules did not prompt. In one of our runs, a skill shipped in a repository ran its bundled script and sent a planted fake credential to a listener on the test machine, despite the deny rules.

The fix. Pull request #4757, "fix: apply configured permission rules when an agent starts", was merged on 9 November and released in 2.6.0. The release notes list it as a normal fix, with no security note, and the advisory has not been published.

Our retest. On 14 November 2026 we reran our original test on Kimi Code 2.6.2, the latest release: shell, read and write deny rules were enforced ("denied by permission rule") and ask rules prompted. The same test on 2.1.1 still ran the denied command.

Timeline - 22 Jul 2026: related public report, #2070 (interactive sessions) - 9 Oct 2026: we report to Moonshot by email (2.1.1) - 26 Oct 2026: related public reports, #4420 and #4437 (print mode) - 8 Nov 2026: we file GitHub advisory GHSA-cmmx-h9w3-462x (2.5.2) - 9 Nov 2026: fix merged (PR #4757) - 12 Nov 2026: fix released in 2.6.0 - 14 Nov 2026: our retest on 2.6.2 confirms the fix