← All advisories
CVE-2026-133198highCode execution2026-11-19

JetBrains Junie: seven new CVEs, from fork code and command injection in the GitHub Action to agent file writes outside the project and code execution via project terminal settings (CVE-2026-133192 to 133198)

On 19 November 2026 JetBrains published seven more CVEs for its Junie AI coding agent, covering the Junie GitHub Action, Junie CLI and the Junie IDE plugin. The two rated high are code execution via terminal environment settings in project files (Junie before 252.819.35 / 253.819.35) and agent file tools modifying files outside the project directory (Junie CLI before 26.6.29). Upgrade the GitHub Action to 1.10.0, Junie CLI to 26.11.1 and the IDE plugin to 252.819.35 / 253.819.35 or later.

01.

What it is

CVE-2026-133198 (7.8, CWE-15): in Junie before 252.819.35 and 253.819.35, code execution was possible via terminal environment settings in project files.

CVE-2026-133195 (7.5, CWE-73): in Junie CLI before 26.6.29, the agent's file tools could modify files outside the project directory.

CVE-2026-133196 (5.3, CWE-184): in Junie CLI before 26.11.1, files outside the project could be overwritten via shell output redirection.

CVE-2026-133197 (5.0, CWE-78): in Junie CLI before 26.9.22, command injection was possible via file names in code review.

Junie GitHub Action before 1.10.0: CVE-2026-133192 (4.2, CWE-829) untrusted fork code could be processed in privileged workflow runs; CVE-2026-133193 (5.6, CWE-23) code execution via path traversal in feedback session markers; CVE-2026-133194 (5.6, CWE-78) command injection via the action version input.

JetBrains lists these on its Fixed security issues page; the one-line descriptions above are all the detail it has published.

02.

How to check

  1. In your repositories, find workflows that use the Junie GitHub Action and check the pinned version (anything below 1.10.0 is affected).
  2. Check your Junie CLI version and the Junie plugin version in your JetBrains IDEs.
  3. Be careful opening untrusted repositories with Junie: two of these issues are triggered by project files or file names.
03.

How to fix

  1. Update the Junie GitHub Action to 1.10.0 or later, and avoid running it with secrets on pull_request_target or other privileged triggers for fork PRs.
  2. Update Junie CLI to 26.11.1 or later (covers the 26.6.29 and 26.9.22 fixes too).
  3. Update the Junie IDE plugin to 252.819.35 / 253.819.35 or later.
# Junie GitHub Action versions used in this repo
grep -rn 'junie' .github/workflows/ 2>/dev/null
junie --version
04.

Sources

Related on VibeVulns
More advisories for this tool
The weekly email

One email a week. Only what changed.

Every new security hole in AI coding tools, MCP servers, app builders and the stacks they generate (Next.js, Supabase, Node, PHP), each with how to check your app and the fix. No roundups of things you already read.

Free, one email a week. Read the latest issue first if you like. One-click unsubscribe in every email. We never sell or share addresses.