# CVE-2026-123022: agentscope-ai AgentScope MCP Workspace API _config.py subprocess.Popen os command 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:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 5 Nov 2026
- **Updated:** 5 Nov 2026
- **Also known as:** GHSA-m997-8g56-6phf

## What is CVE-2026-123022?

CVE-2026-123022 is a medium-severity vulnerability in agentscope-ai AgentScope, published on 5 Nov 2026. 

### Official description

A vulnerability was detected in agentscope-ai AgentScope up to 2.0.11. The impacted element is the function subprocess.Popen of the file src/agentscope/mcp/_config.py of the component MCP Workspace API. The manipulation of the argument command results in os command injection. The attack may be launched remotely. The exploit is now public and may be used. The pull request to fix this issue awaits acceptance.

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

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


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

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

## Is CVE-2026-123022 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123022 is a medium-severity vulnerability in agentscope-ai AgentScope, published on 5 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123022 in the wild and no public exploit code.

Affected product: agentscope-ai AgentScope. 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-123022/ (Markdown: https://insights.sbomify.com/CVE-2026-123022/index.md)
```

## Sources

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

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