dbcve.org
Intellij IdeaApplication · Jetbrains

CVE-2026-59792

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-10
Fix available
A fix is available. Upgrade to 2026.1.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 6 weeks old

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 IntelliJ IDEA before 2026.1.4, 2026.2 code execution via path traversal in project workspace ID handling was possible

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

A path traversal vulnerability in JetBrains IntelliJ IDEA's project workspace ID handling allows attackers to execute arbitrary code. The vulnerability exists in versions prior to 2026.1.4 and enables malicious workspace configurations to traverse filesystem paths and inject executable content.

MitigationUpgrade IntelliJ IDEA to version 2026.1.4 or later to patch the path traversal vulnerability. Restrict access to project workspace directories and validate workspace IDs in development environments.

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
Intellij IdeaApplication
Affected:< 2026.1.4

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Identify IntelliJ IDEA installation and version
    Locate the IntelliJ IDEA installation directory and check the version. On Windows, common paths are C:\Program Files\JetBrains\IntelliJ IDEA or in the user's AppData. On macOS, check /Applications or ~/Library/Application Support/JetBrains. On Linux, check /opt or ~/snap. Look for a version file or check the IDE's about dialog information.
    Affected if The installed version is any version below 2026.1.4
  2. Verify project workspace directory exists
    Check for the presence of workspace storage directories. In IntelliJ projects, workspace data is typically stored in .idea/workspace.xml or similar workspace storage files under the project directory. Locate any project directories that contain IntelliJ workspace configuration.
    Affected if A project workspace directory exists and is being used by the IDE
  3. Examine workspace ID configuration files
    Inspect the .idea/workspace.xml file or other workspace storage files in project directories. Look for workspaceId elements or identifiers that may be used in file path construction. These files are typically XML files in the .idea folder of an IntelliJ project.
    Affected if Workspace ID configuration files are present and contain user-controlled identifiers
  4. Check for file write operations in recent IDE activity
    Review IDE logs (idea.log) for any file write operations involving workspace paths. The logs are typically found in the IDE's log directory (help > Show Log in Explorer). Look for file path constructions that might include workspace identifiers.
    Affected if The IDE has been used to open projects and log entries show workspace-related file operations

You are affected if IntelliJ IDEA version is below 2026.1.4 and you have used the IDE to open projects with workspace files, as the path traversal in workspace ID handling can be triggered during normal IDE operation.

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.4 or later
Fixed in 2026.1.4
Interim mitigation

Upgrade IntelliJ IDEA to version 2026.1.4 or later to patch the path traversal vulnerability. Restrict access to project workspace directories and validate workspace IDs in development environments.

Recommended fix High confidence

2026.1.4

  1. Open IntelliJ IDEA and navigate to Help > Check for Updates (or IntelliJ IDEA > Check for Updates on macOS)
  2. In the update dialog, if version 2026.1.4 or later is available, click Download and Install
  3. Alternatively, download IntelliJ IDEA 2026.1.4 or later directly from www.jetbrains.com/idea/download
  4. If using a custom plugin repository, verify all plugins are compatible with the new version before upgrading
  5. After upgrading, restart IntelliJ IDEA to complete the installation
  6. Verify the installation by checking Help > About shows version 2026.1.4 or later
Caveat IDE upgrades may require adjustment of custom plugins or settings; review plugin compatibility before upgrading

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

Fix this in Intellij Idea Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-59792 — 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-59792 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