Claude Code 2.1.289 closes a second route past its rm guard, and stable is four builds behind

Claude Code 2.1.289 closes a second route past its rm guard, and stable is four builds behind

Claude Code 2.1.289 reached npm on October 3 at 20:12 UTC, and it closes a second route for a deletion command to slip past the permission check that is supposed to stop it. Anthropic's changelog describes the fix as "Fixed Bash deny and ask rules missing a command behind an environment variable prefix with an expanded value (e.g. TZ=\"$HOME\" rm -rf build) when the sandbox auto-allows commands".

Claude Code

Claude Code checks a shell command against its permission rules before it runs.

Anyone installing from the stable channel does not have that fix. At 23:58 UTC on October 4 the npm registry's dist-tags for the package still pointed stable at 2.1.285, while latest and next both sat on 2.1.289, four releases ahead.

Anthropic does not call either of the sandbox fixes a vulnerability. There is no CVE, no severity rating, and nothing in the changelog in Anthropic's own repository that says the path was ever used against anyone.

Both Bash fixes apply only under sandbox auto-allow

Anthropic scopes both of them to one situation. One applies "when the sandbox auto-allows commands", and the other covers "a Bash deny or ask rule being skipped under sandbox auto-allow when a bare variable assignment came before the command". Neither describes a default install with no sandbox in play.

A deny or ask rule matches on the command it expects to find at the front of the line, and an environment-variable assignment in front of it gives the shell something to read first. The previous release fixed the same guard against a different trick, where a bash -c wrapper got a dangerous rm past it, which we covered on October 3.

Managed machines get a third shell fix. A deny or ask rule on a nested part of a compound shell command was "not holding over a user-installed mod's approval on managed machines".

A plugin could rewrite an admin-installed server's sign-in text

The release also fixes something that has nothing to do with the shell. Anthropic records "Fixed a user-installed plugin being able to rewrite the descriptions of an organization-managed MCP server's sign-in tools".

Tool descriptions are the text a model reads to work out what a tool does and when to reach for it, so a description is instructions rather than decoration. An MCP server installed by an organisation's administrators is the half of that pairing a user is not supposed to be able to edit, and a sign-in tool is the one that asks for credentials. Anthropic says only that a user-installed plugin could change that text, not whether any plugin did.

File reads get a fix as well: Read deny rules were "not applying to files @-mentioned, changed, or selected in the IDE through a symlink". Five of the release's 27 fixes are permission or sandbox work, and most of the rest repair the plugin interface, including a freeze at launch when a plugin drew a border style the terminal does not know.

Stable has not moved since September 29

2.1.285 was published on September 29 at 17:32 UTC, and the four releases since have arrived at close to one a day: 2.1.286 on September 30 at 17:14 UTC, 2.1.287 on October 1 at 16:59 UTC, 2.1.288 on October 2 at 18:30 UTC and 2.1.289 on October 3 at 20:12 UTC. Anyone who installs from the stable tag gets none of the five permission fixes in the newest build.

That is a choice about release channels rather than a defect, and a conservative stable tag is the normal reason to have one. Anthropic publishes no schedule for promoting a build, so the gap is visible in the registry and nowhere else. The fix 2.1.289 flags for its own users is a smaller one: installed mods were not loading in the first session after an upgrade, which is the session in which someone would go looking for what changed.

Leave a Comment

Your email address will not be published. Required fields are marked *