# CVE-2025-27106: Code injection in binance-trading-bot

> Authenticated users can execute arbitrary code on the host via command injection in the restore endpoint of the Binance trading bot.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Feb 2025
- **Updated:** 22 Feb 2025
- **Also known as:** GHSA-wq6j-4388-4gg5

## What is CVE-2025-27106?

CVE-2025-27106 is a high-severity command injection vulnerability in chrisleekr binance-trading-bot, published on 21 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

binance-trading-bot is an automated Binance trading bot with trailing buy/sell strategy. Authenticated users of binance-trading-bot can achieve Remote Code Execution on the host system due to a command injection vulnerability in the `/restore` endpoint. The restore endpoint of binance-trading-bot is vulnerable to command injection via the `/restore` endpoint. The name of the uploaded file is passed to shell.exec without sanitization other than path normalization, resulting in Remote Code Execution. This may allow any authorized user to execute code in the context of the host machine. This issue has been addressed in version 0.0.100 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2025-27106 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-27106 is a high-severity command injection vulnerability in chrisleekr binance-trading-bot, published on 21 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-27106 in the wild and no public exploit code.

Affected product: chrisleekr binance-trading-bot. 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-27106/ (Markdown: https://insights.sbomify.com/CVE-2025-27106/index.md)
```

## Sources

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

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