dbcve.org
GolandApplication · Jetbrains

CVE-2026-53915

HIGH · 8.8 CVSS v3.1 Published 2026-06-19
Fix available
A fix is available. Upgrade to 2026.1.3 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In JetBrains GoLand before 2026.1.3 remote code execution was possible via untrusted project configuration

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Remote code execution vulnerability in JetBrains GoLand IDE (versions before 2026.1.3) that allows attackers to execute arbitrary code on target systems by exploiting untrusted project configuration files.

MitigationUpgrade to GoLand 2026.1.3 or later. Avoid opening projects from untrusted sources until the update is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GolandApplication
Affected:< 2026.1.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify GoLand is installed
    Look for the GoLand IDE installation directory. On Windows, check C:\Program Files\JetBrains\GoLand or %LOCALAPPDATA%\JetBrains\GoLand. On macOS, check /Applications/GoLand.app. On Linux, check ~/JetBrains/GoLand or /opt/GoLand.
    Affected if GoLand IDE is present on the system
  2. Identify the installed GoLand version
    Open GoLand and navigate to Help > About to view the exact version number. Alternatively, check the installation directory for a version file or use the command line: on Windows run 'goland64.exe version', on macOS run 'grep -i version /Applications/GoLand.app/Contents/Info.plist', on Linux check the version in the installation folder name or run the launcher with a version flag.
    Affected if Version cannot be determined or is displayed as a pre-2026 release
  3. Compare version against affected range
    If the version is displayed, compare it to the affected range: any version before 2026.1.3 is vulnerable. Versions 2026.1.3 and later are not affected. Note that versions are typically shown as numbers like 2026.1, 2026.1.1, 2026.1.2, or 2026.1.3.
    Affected if Installed version is less than 2026.1.3 (for example, 2026.1, 2026.1.1, 2026.1.2, or any 2025.x release)
  4. Assess exposure to untrusted project files
    The vulnerability is triggered when opening projects from untrusted or unverified sources. Consider whether you or your team commonly open GoLand project files (.go, .idea, or project directories) obtained from external parties, downloads, or untrusted repositories.
    Affected if Users routinely open GoLand projects from untrusted or unknown sources without verification

A user is affected if GoLand is installed with any version prior to 2026.1.3 AND the IDE is used to open projects from untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2026.1.3 or later
Fixed in 2026.1.3
Interim mitigation

Upgrade to GoLand 2026.1.3 or later. Avoid opening projects from untrusted sources until the update is applied.

Recommended fix High confidence

GoLand 2026.1.3 or later

  1. Open GoLand IDE
  2. Navigate to Help > Check for Updates (or GoLand > Check for Updates on macOS)
  3. If an update is available, download and install GoLand 2026.1.3 or later
  4. Alternatively, download the latest version from the official JetBrains website: www.jetbrains.com/go/download/
  5. Restart the IDE after installation to apply the security fix

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Goland Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53915 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53915 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data