ToolboxApplication · Jetbrains

CVE-2025-43012

CRITICAL · 9.8 CVSS v3.1 Published 2025-04-17
Fix available
A fix is available. Upgrade to 2.6 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 Toolbox App before 2.6 command injection in SSH plugin 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 command injection vulnerability exists in the SSH plugin of JetBrains Toolbox App versions prior to 2.6. The vulnerability allows attackers to execute arbitrary commands on the target system through the SSH functionality, likely due to insufficient input validation when handling SSH connection parameters or commands.

MitigationUpgrade JetBrains Toolbox App to version 2.6 or later to remediate this vulnerability. Until the upgrade is applied, avoid using the SSH plugin with untrusted connections.

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
ToolboxApplication
Affected:< 2.6

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. Locate JetBrains Toolbox installation
    Search for the JetBrains Toolbox executable (toolbox.exe on Windows, JetBrains Toolbox on macOS/Linux) in common installation directories such as %LOCALAPPDATA%\JetBrains\Toolbox on Windows, /Applications on macOS, or ~/.local/share/JetBrains/Toolbox on Linux. Also check if installed via snap, flatpak, or other package managers.
    Affected if JetBrains Toolbox is installed on the system
  2. Determine installed version
    Right-click the toolbox executable and select Properties > Details on Windows to view the File Version. On macOS, right-click the app > Get Info to see the Version. On Linux, check the version within the application itself via Help > About, or inspect the .version file in the installation directory.
    Affected if The version number is lower than 2.6 (e.g., 2.5.x, 2.4.x, 1.x, etc.)
  3. Identify SSH plugin status
    Open JetBrains Toolbox and navigate to Settings or Preferences. Look for the SSH plugin or SSH functionality listed under Plugins, Tools, or Settings. On the Tools tab, check if SSH-related integration is enabled or configured.
    Affected if The SSH plugin is present, enabled, or has been used at least once to manage SSH connections
  4. Confirm vulnerability applicability
    Review the context: this vulnerability specifically affects the SSH plugin functionality. If you have used or configured SSH connections through JetBrains Toolbox (e.g., for cloning repositories or SSH shortcuts), the attack surface is present.
    Affected if The SSH plugin is in use and the installed version is below 2.6

A user is affected if JetBrains Toolbox version 2.6 or later is NOT installed AND the SSH plugin has been enabled or used on the system.

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 2.6 or later
Fixed in 2.6
Interim mitigation

Upgrade JetBrains Toolbox App to version 2.6 or later to remediate this vulnerability. Until the upgrade is applied, avoid using the SSH plugin with untrusted connections.

Recommended fix High confidence

2.6

  1. Open JetBrains Toolbox App
  2. Click on the settings icon (gear) or navigate to the Toolbox settings
  3. Check for updates or navigate to the version information
  4. Update to version 2.6 or later
  5. Restart the application to ensure the update is fully applied

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

Fix this in Toolbox Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $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 $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2025-43012 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