Security readout for executives and security teams
Plain-English summary
A malicious or compromised Go project could make GoLand run code before the user approves trusting that project. Successful exploitation could expose developer credentials and source code, alter files, or disrupt the workstation. The user must open the project, but no prior account privileges are required.
Executive priority
Prioritize prompt remediation on developer workstations because they commonly hold source code, tokens, signing material, and production access. Accelerate action for teams that evaluate external repositories or accept contributed Go projects. Broad emergency response is not supported without evidence of exploitation, but affected systems should not continue opening untrusted projects.
Technical view
CVE-2026-64802 is a CWE-94 code-injection flaw in GoLand’s Go Modules integration before version 2026.2. It permits arbitrary code execution before the project-trust decision. CVSS 3.1 rates it 7.8: local attack vector, low complexity, no privileges, required user interaction, unchanged scope, and high confidentiality, integrity, and availability impacts.
Likely exposure
Exposure is likely limited to systems running GoLand versions earlier than 2026.2 where users open untrusted, externally sourced, or compromised Go projects. The supplied affected-version metadata is inconsistent, listing version “0” while the description states “before 2026.2”; inventory validation should therefore use the descriptive version boundary and vendor guidance.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not listed as KEV in the bundle. Exploitation requires a user to open a crafted or compromised project locally. The weakness is significant because execution can occur before GoLand presents or enforces its project-trust boundary.
Researcher notes
The public bundle provides only a concise description and CVSS vector; it does not document the vulnerable execution path, affected operating systems, indicators, or exploitation evidence. The stated boundary is GoLand before 2026.2, despite inconsistent structured affected-version data. Validation should avoid destructive testing and rely on version inventory, vendor confirmation, and endpoint telemetry.
Mitigation direction
- Upgrade GoLand to version 2026.2 or later after confirming vendor guidance.
- Until upgraded, avoid opening Go projects from untrusted or unverifiable sources.
- Treat externally supplied repositories as potentially hostile and review their provenance outside vulnerable GoLand versions.
- Investigate developer workstations that recently opened suspicious projects while running an affected version.
Validation and detection
- Inventory installed GoLand versions and identify releases earlier than 2026.2.
- Confirm upgraded installations report GoLand 2026.2 or later.
- Review project acquisition records for untrusted repositories opened on affected systems.
- Check endpoint telemetry for unexpected processes or file changes associated with affected GoLand sessions.
- Verify the vendor fixed-issues page for any additional remediation or detection guidance.
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-64802 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.