# CVE-2026-10214: zhayujie chatgpt-on-wechat Bash Tool bash.py _get_safety_warning 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:** 1 Jun 2026
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-qvrw-783g-pmvr

## What is CVE-2026-10214?

CVE-2026-10214 is a medium-severity vulnerability in zhayujie chatgpt-on-wechat, published on 1 Jun 2026. 

### Official description

A weakness has been identified in zhayujie chatgpt-on-wechat up to 2.0.8. This issue affects the function _get_safety_warning of the file agent/tools/bash/bash.py of the component Bash Tool. Executing a manipulation can lead to os command injection. The attack can be launched remotely. The exploit has been made available to the public and could be used for attacks. Upgrading to version 2.0.9 is capable of addressing this issue. This patch is called 16d9b449c9aa53ccee44144a762a2737d7ba4fc4. It is recommended to upgrade the affected component.

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-10214?


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

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

## Is CVE-2026-10214 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10214 is a medium-severity vulnerability in zhayujie chatgpt-on-wechat, published on 1 Jun 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10214 exists.

Affected product: zhayujie chatgpt-on-wechat. 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-10214/ (Markdown: https://insights.sbomify.com/CVE-2026-10214/index.md)
```

## Sources

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

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