Security readout for executives and security teams
Plain-English summary
GoLand versions before 2026.2 could run arbitrary code through the configured Go SDK before a user approved project trust. A malicious or compromised project could therefore affect a developer workstation when opened, potentially exposing data, altering files, or disrupting the system.
Executive priority
Treat this as a high-priority developer-endpoint update. Accelerate remediation where GoLand users possess valuable source code or privileged credentials. Immediate emergency response is not supported by the supplied exploitation evidence, but the potential impact of successful code execution is substantial.
Technical view
CVE-2026-64803 is a CWE-94 code-injection issue in JetBrains GoLand before 2026.2. It has CVSS 3.1 score 7.8: local access, low complexity, no privileges, and user interaction required, with high confidentiality, integrity, and availability impact. The sources do not describe the precise execution path.
Likely exposure
Exposure is most likely on developer systems running GoLand earlier than 2026.2, particularly where users open projects from untrusted or compromised sources and a configured Go SDK is present. The supplied affected-version metadata is inconsistent, listing version "0," so organizations should verify applicability against JetBrains guidance.
Exploitation context
The CVSS vector indicates a local, user-assisted attack rather than direct remote exploitation. Code execution could occur before project trust was granted. The supplied record is not in CISA KEV, and no source in the bundle reports active exploitation or provides evidence of public weaponization.
Researcher notes
The public bundle attributes execution to the configured Go SDK before project-trust approval but does not document root cause, affected operating systems, indicators, or exploit availability. CVSS implies local access and required user interaction. The anomalous affected-version value prevents precise range validation beyond the stated "before 2026.2" boundary.
Mitigation direction
- Upgrade JetBrains GoLand to version 2026.2 or later.
- Until upgraded, avoid opening projects from untrusted or unverified sources.
- Check JetBrains security guidance for any additional product-specific precautions.
- Prioritize developer workstations handling source code, credentials, signing keys, or production access.
Validation and detection
- Inventory installed GoLand versions and identify releases earlier than 2026.2.
- Confirm upgraded installations report GoLand 2026.2 or later.
- Review developer workflows for recently opened untrusted or externally sourced projects.
- Investigate affected endpoints for unexpected activity; the sources provide no specific indicators of compromise.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-64803 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9JetBrainsVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.jetbrains.com/privacy-security/issues-fixed/CVE reference, JetBrains
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.