CVE-2025-58335 Overview
CVE-2025-58335 is an information disclosure vulnerability in JetBrains Junie, an AI coding agent that integrates with JetBrains IDEs. The flaw resides in the search_project function and allows unauthorized access to project information. JetBrains addressed the issue across multiple Junie release branches, including 252.284.66, 251.284.66, 243.284.66, and earlier builds in the 252, 251, and 243 lines. The vulnerability is classified under [CWE-356] (Product UI does not Warn User of Unsafe Actions) and is exploitable remotely without authentication or user interaction.
Critical Impact
An unauthenticated remote attacker can extract sensitive project information through the search_project function, exposing confidentiality of developer workspace data.
Affected Products
- JetBrains Junie versions prior to 252.284.66, 251.284.66, and 243.284.66
- JetBrains Junie versions prior to 252.284.61, 251.284.61, and 243.284.61
- JetBrains Junie versions prior to 252.284.54, 252.284.50, 251.284.54, 251.284.50, 243.284.54, and 243.284.50
Discovery Timeline
- 2025-08-28 - CVE-2025-58335 published to NVD
- 2026-01-20 - Last updated in NVD database
Technical Details for CVE-2025-58335
Vulnerability Analysis
JetBrains Junie is an AI-powered coding agent that performs autonomous actions within developer projects, including searching and reading project files. The vulnerability resides in the search_project function, which exposes project information without enforcing adequate safeguards. An attacker can invoke this function to retrieve content that should remain confined to the local project context.
The weakness maps to [CWE-356], indicating that Junie does not sufficiently warn or restrict the user when potentially unsafe project searches are performed. The result is unintended exposure of source code, configuration, or other artifacts stored within the project workspace. Only confidentiality is affected by this flaw; integrity and availability of the system remain intact.
Root Cause
The root cause is improper boundary enforcement within the search_project function. The function services queries against project content without applying sufficient access constraints or user-confirmation safeguards before returning data. This permits requests that read material outside the intended scope of a single safe search operation.
Attack Vector
The vulnerability is exploitable over the network without authentication or user interaction. An attacker can craft requests that exercise the search_project function to retrieve project contents. Because Junie operates as an AI agent that processes external inputs, attacker-controlled prompts or content can drive the function into disclosing project data.
No public proof-of-concept code is available for this issue. Refer to the JetBrains Security Issues Fixed advisory for vendor technical context.
Detection Methods for CVE-2025-58335
Indicators of Compromise
- Unexpected outbound network connections from JetBrains IDE processes hosting the Junie plugin to unknown endpoints.
- Abnormal Junie agent activity invoking search_project against directories outside active developer focus.
- Junie plugin versions matching the vulnerable builds in the 252.284.x, 251.284.x, or 243.284.x ranges prior to the fixed releases.
Detection Strategies
- Inventory installed Junie plugin versions across developer workstations and compare against the fixed versions listed in the JetBrains advisory.
- Monitor JetBrains IDE process telemetry for unusual file enumeration patterns originating from the Junie agent.
- Review AI agent logs and prompt histories for queries that target sensitive paths such as configuration files, credential stores, or .env files.
Monitoring Recommendations
- Collect endpoint process and file-access telemetry from developer machines into a centralized data lake for correlation.
- Alert on Junie plugin reads of files containing secrets, tokens, or private keys.
- Track plugin update compliance and flag endpoints running unpatched Junie builds.
How to Mitigate CVE-2025-58335
Immediate Actions Required
- Update JetBrains Junie to a fixed build (252.284.66, 251.284.66, 243.284.66, or later) on all developer endpoints.
- Audit projects opened with vulnerable Junie versions for exposure of credentials, API keys, or proprietary source.
- Rotate any secrets stored in repositories that may have been processed by the vulnerable search_project function.
Patch Information
JetBrains has released fixed versions across the 252, 251, and 243 branches. Refer to the JetBrains Security Issues Fixed page for the authoritative list of patched builds and update guidance.
Workarounds
- Disable or uninstall the Junie plugin on systems that cannot be updated immediately.
- Restrict Junie usage to projects that do not contain sensitive credentials or regulated data until patching completes.
- Apply egress network controls on developer workstations to limit AI agent communication to approved endpoints.
# Verify installed Junie plugin version on a JetBrains IDE
ls ~/.local/share/JetBrains/*/plugins/ | grep -i junie
# On macOS
ls ~/Library/Application\ Support/JetBrains/*/plugins/ | grep -i junie
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
