# CVE-2025-43012: In JetBrains Toolbox App before 2.6 command injection in SSH plugin was possible


- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Apr 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-xxvv-rw24-p2j6

## What is CVE-2025-43012?

CVE-2025-43012 is a high-severity vulnerability in JetBrains Toolbox App, published on 17 Apr 2025. 

### Official description

In JetBrains Toolbox App before 2.6 command injection in SSH plugin was possible

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2025-43012?

It affects 1 product.


Products: Jetbrains Toolbox.

## How do I fix CVE-2025-43012?

No fix has been published for CVE-2025-43012 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-43012 being exploited?

There is no known exploitation of CVE-2025-43012 in the wild and no public exploit code.

## Other vulnerabilities in JetBrains Toolbox App

- [CVE-2020-25207](https://insights.sbomify.com/CVE-2020-25207/): Code injection in n/a (critical 9.8)
- [CVE-2020-25013](https://insights.sbomify.com/CVE-2020-25013/): Denial of service in n/a (high 7.5)
- [CVE-2020-15827](https://insights.sbomify.com/CVE-2020-15827/): Security feature bypass in n/a (high 7.5)
- [CVE-2019-18368](https://insights.sbomify.com/CVE-2019-18368/): Privilege escalation in n/a (high 7.3)
- [CVE-2025-43013](https://insights.sbomify.com/CVE-2025-43013/): Weak cryptography in Toolbox App (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-43012 and fix it if it is affected.

What it is: CVE-2025-43012 is a high-severity vulnerability in JetBrains Toolbox App, published on 17 Apr 2025. 
Exploitation: There is no known exploitation of CVE-2025-43012 in the wild and no public exploit code.

Affected product: JetBrains Toolbox App. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-43012/ (Markdown: https://insights.sbomify.com/CVE-2025-43012/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-43012
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-43012
- OSV: https://osv.dev/vulnerability/CVE-2025-43012

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-43012/
Summaries are generated and may contain mistakes; the official description above is the record.