Safeguard
AI Security•

Version floors for AI coding agents: a check script and the August 2026 numbers

Claude Code 2.1.163, Gemini CLI 0.39.1, run-gemini-cli 0.1.22 and Cursor 3.0 all carry fixes for 2026 agent flaws. Here is how to enforce those minimums in CI and on laptops.

Safeguard Security Team
3 min read

Between June and August 2026, several AI coding agents received fixes for flaws that let untrusted text lead to code execution or data theft. The fixes sit at specific versions: Claude Code 2.1.163, Gemini CLI 0.39.1, the run-gemini-cli GitHub Action 0.1.22, and Cursor 3.0. The most recent of these became public on 5 August 2026, when Novee Security presented at Black Hat USA.

A version floor is a minimum version your tooling enforces. Developer tools update themselves, until they do not, and pinned CI images never do.

What's affected

ToolFloorFixes (identifiers)
Claude Code2.1.163CVE-2026-55607 worktree sandbox escape, CVE-2026-54316 WebFetch exfiltration
Gemini CLI (npm)0.39.1CVE-2026-12537
run-gemini-cli (Action)0.1.22CVE-2026-12537
Cursor3.0CVE-2026-50548 and CVE-2026-50549

What to do now

Start with a script that reports installed versions on a laptop or build image:

#!/usr/bin/env bash
check() { # name, installed, floor
  if [ -z "$2" ]; then echo "$1: not installed"; return; fi
  if [ "$(printf '%s\n%s\n' "$3" "$2" | sort -V | head -1)" = "$3" ]; then
    echo "$1: $2 OK (floor $3)"
  else
    echo "$1: $2 BELOW FLOOR $3"
  fi
}
claude_v=$(claude --version 2>/dev/null | grep -oE '[0-9]+\.[0-9]+\.[0-9]+' | head -1)
gemini_v=$(gemini --version 2>/dev/null | grep -oE '[0-9]+\.[0-9]+\.[0-9]+' | head -1)
check "Claude Code" "$claude_v" 2.1.163
check "Gemini CLI" "$gemini_v" 0.39.1

Then do the same for pipelines, which is where old versions hide:

grep -rnE "gemini_cli_version|run-gemini-cli@|claude-code@|@anthropic-ai/claude-code" .github/workflows/ Dockerfile* 2>/dev/null
  1. Add the check to onboarding scripts and to a scheduled job on managed devices.
  2. Replace floating or old pinned versions in workflow files and Dockerfiles with versions at or above the floors.
  3. Keep a short table like the one above in your engineering docs and update it when a new advisory lands.
  4. For Cursor, read the version in the application; Cursor 3.0 shipped on 2 April 2026.
  5. Treat a version bump as one control among several. Narrow permissions and egress limits still matter after patching.

Quick check

Which minimum Claude Code version covers both CVE-2026-55607 and CVE-2026-54316?

2.1.163.

Sources

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.