In JetBrains Junie CLI before 26.9.22 command injection was possible via file names in code review
Search vulnerabilities
In JetBrains Junie GitHub Action before 1.10.0 code execution was possible via path traversal in feedback session markers
In JetBrains Junie GitHub Action before 1.10.0 command injection was possible via the action version input
In JetBrains Junie CLI before 26.11.1 files outside the project could be overwritten via shell output redirection
In JetBrains Junie GitHub Action before 1.10.0 untrusted fork code could be processed in privileged workflow runs
Unauthorized File Modification via Agent Tools in JetBrains Junie CLI
In JetBrains Junie CLI before 26.6.29 files outside the project directory could be modified by agent file tools
In JetBrains Junie before 252.819.35, 253.819.35 code execution was possible via terminal environment settings in project files
Exposure of Sensitive Environment Variables in Session Event Logs
In JetBrains Junie CLI before 26.6.29 sensitive environment variables were exposed in session event logs
Command Execution via Allow Similar Commands Option in JetBrains Junie CLI
In JetBrains Junie CLI before 26.8.24 command execution was possible via the Allow Similar Commands option
HTML-Encoded Prompt Injection Evasion in JetBrains Junie GitHub Action
In JetBrains Junie GitHub Action before 1.6.4 prompt injection protection could be bypassed via HTML-encoded characters
Remote Code Execution via Fork Updates in JetBrains Junie GitHub Action
In JetBrains Junie GitHub Action before 1.8.0 code execution with workflow credentials was possible via fork updates
Command Execution via Insufficient Allowlist Validation in JetBrains Junie CLI
In JetBrains Junie CLI before 26.8.17 command execution was possible due to incomplete validation of allowlisted commands
Command Injection via Malicious Project File in JetBrains Junie
In JetBrains Junie before 252.549.29 command execution was possible via malicious project file
In JetBrains Junie before 252.284.66, 251.284.66, 243.284.66, 252.284.61, 251.284.61, 243.284.61, 252.284.50, 252.284.54, 251.284.54, 251.284.50, 243.284.54, 243.284.50 information disclosure was possible via search_project function
In JetBrains Junie before 252.284.66, 251.284.66, 243.284.66, 252.284.61, 251.284.61, 243.284.61, 252.284.50, 252.284.54, 251.284.54, 251.284.50, 243.284.54, 243.284.50 code execution was possible due to improper command validation