CVE-2026-86502

8.4

JetBrains · IntelliJ IDEA

A missing TLS and authentication implementation in the IntelliJ IDEA IJent gRPC server allows local code execution on Remote Development hosts.

Executive summary

A critical vulnerability in JetBrains IntelliJ IDEA allows unauthenticated local attackers to achieve code execution on Remote Development hosts.

Vulnerability

This vulnerability, categorized as CWE-306 (Missing Authentication for Critical Function), exists within the IJent gRPC server component. The lack of proper TLS encryption and authentication mechanisms permits an unauthenticated local attacker to interact with the service and execute arbitrary code.

Business impact

The ability for a local attacker to execute arbitrary code poses a severe risk to the integrity and confidentiality of the development environment. Successful exploitation could lead to unauthorized access to source code, credentials stored within the IDE, and potential lateral movement into the broader corporate network. With a CVSS score of 8.4, this high-severity vulnerability requires immediate attention to prevent compromise of development infrastructure.

Remediation

Immediate Action: Update JetBrains IntelliJ IDEA to version 2026.2.2 or later to apply the necessary authentication and encryption fixes.

Proactive Monitoring: Review system access logs for unauthorized connections to the IJent gRPC service port, particularly from non-privileged local processes.

Compensating Controls: If an immediate update is not feasible, restrict local user permissions to prevent untrusted processes from executing and limit access to the specific gRPC server ports used by the IDE.

Exploitation status

Public Exploit Available: No (exploit_available: false)

Analyst recommendation

Given the high CVSS score and the direct impact on code execution, organizations utilizing IntelliJ IDEA for Remote Development must prioritize this update. Applying the 2026.2.2 patch is the only effective way to remediate the underlying authentication deficiency and secure the development environment against local exploitation attempts.

More JetBrains CVEs all →

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources