# CVE-2025-46070: Code injection in n/a

> A remote attacker can execute arbitrary code in Automai BotManager via the BotManager.exe component.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jan 2026
- **Updated:** 12 Jan 2026
- **Also known as:** GHSA-mp53-vxqr-3f76

## What is CVE-2025-46070?

CVE-2025-46070 is a critical code injection vulnerability in n/a, published on 12 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in Automai BotManager v.25.2.0 allows a remote attacker to execute arbitrary code via the BotManager.exe component

Weakness: CWE-295 (Improper Certificate Validation)

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

It affects 1 product.


Products: Automai Botmanager.

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

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

## Is CVE-2025-46070 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-46070 is a critical code injection vulnerability in n/a, published on 12 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-46070 in the wild and no public exploit code.

Affected product: n/a. 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-46070/ (Markdown: https://insights.sbomify.com/CVE-2025-46070/index.md)
```

## Sources

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

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