# CVE-2026-123675: OpenBMB Internet of Agents Code Executor Tool code_executor.py execute_code code injection


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 6 Nov 2026
- **Updated:** 6 Nov 2026
- **Also known as:** GHSA-w43h-qvhf-jh65

## What is CVE-2026-123675?

CVE-2026-123675 is a medium-severity vulnerability in OpenBMB Internet of Agents, published on 6 Nov 2026. 

### Official description

A flaw has been found in OpenBMB Internet of Agents up to 9d78e88e47160eb42ee1ee8538c05e1c2c47877a. This affects the function execute_code of the file im_client/agents/tools/code_executor.py of the component Code Executor Tool. This manipulation of the argument filename/lang causes code injection. The attack can be initiated remotely. The exploit has been published and may be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2026-123675?


## How do I fix CVE-2026-123675?

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

## Is CVE-2026-123675 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123675 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-123675 and fix it if it is affected.

What it is: CVE-2026-123675 is a medium-severity vulnerability in OpenBMB Internet of Agents, published on 6 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123675 exists.

Affected product: OpenBMB Internet of Agents. 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-2026-123675/ (Markdown: https://insights.sbomify.com/CVE-2026-123675/index.md)
```

## Sources

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

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