# CVE-2026-19266: Kirachon context-engine review-git-diff Endpoint gitUtils.ts execGitCommand command injection


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 8 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-fjwc-rc47-268g

## What is CVE-2026-19266?

CVE-2026-19266 is a medium-severity vulnerability in Kirachon context-engine, published on 8 Aug 2026. 

### Official description

A vulnerability was determined in Kirachon context-engine up to 1.9.0. This affects the function execGitCommand of the file src/mcp/utils/gitUtils.ts of the component review-git-diff Endpoint. Executing a manipulation of the argument args can lead to command injection. Upgrading to version 1.9.1 mitigates this issue. This patch is called e0729dcfd3a2b1682a7bff86e7174852c03419ba. It is advisable to upgrade the affected component.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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


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

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

## Is CVE-2026-19266 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19266 is a medium-severity vulnerability in Kirachon context-engine, published on 8 Aug 2026. 
Exploitation: There is no known exploitation of CVE-2026-19266 in the wild and no public exploit code.

Affected product: Kirachon context-engine. 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-19266/ (Markdown: https://insights.sbomify.com/CVE-2026-19266/index.md)
```

## Sources

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

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