CVE-2026-64803: JetBrains GoLand arbitrary code execution via Go SDK

CVE-2026-64803 · Severity: high · CVSS 7.8 · Published 2026-07-23

JetBrains GoLand, a popular development environment for the Go programming language, contained a vulnerability that could allow malicious code to run on a developer's machine. This could occur when a user opens a project but before they have explicitly granted 'trust' to that project. An attacker could use this to gain full control over the user's workstation, potentially leading to data theft or further network intrusion.

Technologies: Jetbrains GoLand. Vendors: Jetbrains.

Quick answers

Is CVE-2026-64803 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-64803 being exploited in the wild.
How severe is CVE-2026-64803?
High severity, with a CVSS score of 7.8, published 23 July 2026.
Which products and versions are affected?
Jetbrains GoLand before 2026.2.
Is there a fix for CVE-2026-64803?
A patch was published on 2026-07-23: Fixed in version 2026.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-64803 attacked?
It is attacked with local access, in a network appliance.
Am I affected by CVE-2026-64803?
Check whether you run Jetbrains GoLand at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A code injection vulnerability (CWE-94) existed in JetBrains GoLand versions prior to 2026.2. The flaw resided in how the IDE handled the configured Go SDK when opening a project, failing to properly restrict execution until the user explicitly granted project trust. An attacker could exploit this by convincing a user to open a malicious project, leading to arbitrary code execution with the privileges of the IDE user. The vulnerability is addressed in version 2026.2.

Affected products

  • JetBrains GoLand before 2026.2

Timeline

  • 2026-07-23: advisory: NVD record published
  • 2026-07-23: patched: Fixed in version 2026.2

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.