dbcve.org
Intellij IdeaApplication · Jetbrains

CVE-2026-49366

HIGH · 7.8 CVSS v3.1 Published 2026-05-29
Fix available
A fix is available. Upgrade to 2026.1.1 or later.
See remediation →
81/100
Remediation priority · High
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 IntelliJ IDEA before 2026.1.1 command injection was possible via filename completion

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 command injection vulnerability in IntelliJ IDEA's filename completion feature allows attackers to execute arbitrary commands. The issue affects versions prior to 2026.1.1. This is a high-severity (CVSS 7.8) security flaw that could allow an attacker to run commands with the privileges of the user running the IDE.

MitigationUpgrade IntelliJ IDEA to version 2026.1.1 or later to remediate this vulnerability. Avoid using the filename completion feature on untrusted filesystems or project directories until the upgrade 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
Intellij IdeaApplication
Affected:< 2026.1.1

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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. Check IntelliJ IDEA installed version
    Open IntelliJ IDEA and navigate to Help > About (or IntelliJ IDEA > About on macOS). Record the version number shown (e.g., 2026.1.0, 2025.3.5, etc.).
    Affected if The displayed version is earlier than 2026.1.1 (for example, 2026.1.0, 2025.x.x, or any 2024.x.x/2023.x.x release).
  2. Verify version via command line (optional alternative)
    On Windows, check the installation directory (typically C:\Program Files\JetBrains\IntelliJ IDEA*\) for the version folder name. On macOS, right-click the IntelliJ IDEA app in Applications and select Show Package Contents to find version info in Contents/Info.plist or Contents/Resources/. On Linux, check /opt/idea-* or ~/.local/share/JetBrains/Toolbox/apps/IDEA/ for version folders.
    Affected if The discovered version folder or Info.plist entry shows a version number lower than 2026.1.1.
  3. Confirm filename completion usage context
    The vulnerability is triggered when using filename completion (typically via Tab or Ctrl+Space) in contexts where IntelliJ constructs system commands, such as: Run/Debug configurations with shell scripts, Terminal tool windows, or when editing file paths in settings that invoke external tools. Consider whether you frequently use these features.
    Affected if You use IntelliJ IDEA with version below 2026.1.1 AND actively use filename completion in command-related contexts (Run configs, Terminal, external tool paths).

You are affected if your installed IntelliJ IDEA version is any release prior to 2026.1.1 and you use the filename completion feature in contexts involving system command construction.

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.1 or later
Fixed in 2026.1.1
Interim mitigation

Upgrade IntelliJ IDEA to version 2026.1.1 or later to remediate this vulnerability. Avoid using the filename completion feature on untrusted filesystems or project directories until the upgrade is applied.

Recommended fix High confidence

2026.1.1

  1. Open IntelliJ IDEA
  2. Navigate to Help > Check for Updates
  3. Follow the prompts to download and install version 2026.1.1 or later
  4. Alternatively, download the installer directly from jetbrains.com/idea/download and install version 2026.1.1 or later
  5. Restart the IDE after installation
Caveat Review JetBrains release notes for potential plugin compatibility or settings changes between your current version and 2026.1.1

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
  • Implementation2.0 h
  • Testing2.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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