CVE-2026-53915: In JetBrains GoLand before 2026.1.3 remote code execution was possible via untrusted project configuration
CVE-2026-53915 is a high-severity flaw (CVSS 7.1) affecting goland. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
In JetBrains GoLand before 2026.1.3 remote code execution was possible via untrusted project configuration
Why this priority
- High severity
A fixed release or distro patch exists.
Risk facts
| CVSS score | 7.1 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 0.5% (top 61%) |
| CISA exploited list | No |
| Weakness | CWE-73 |
| Published | 2026-06-19 |
| Last modified | 2026-10-26 |
Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-53915?
goland: upgrade to 2026.1.3. Exact commands for each OS are on this page.
Is CVE-2026-53915 being exploited?
CVE-2026-53915 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-53915 affect?
CVE-2026-53915 affects goland. Severity is high (CVSS 7.1). In JetBrains GoLand before 2026.1.3 remote code execution was possible via untrusted project configuration
How urgent is CVE-2026-53915?
Priority 35/100. High severity
Related CVEs
- CVE-2026-64802 HIGH 7.8 UPGRADE In JetBrains GoLand before 2026.2 arbitrary code execution was possible before granting project trust in the G
- CVE-2026-64803 HIGH 7.8 UPGRADE In JetBrains GoLand before 2026.2 arbitrary code execution was possible before granting project trust via the
- CVE-2026-64800 LOW 3.5 UPGRADE In JetBrains GoLand before 2026.2 sensitive configuration values written to log files by default