# CVE-2026-116369: Sunwood-ai-labs github-kanban-mcp-server issue-handlers.ts handleListIssues os command injection


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-q845-6fh7-j6h3

## What is CVE-2026-116369?

CVE-2026-116369 is a medium-severity vulnerability in Sunwood-ai-labs github-kanban-mcp-server, published on 26 Oct 2026. 

### Official description

A vulnerability was identified in Sunwood-ai-labs github-kanban-mcp-server up to 0.4.0. Impacted is the function handleListIssues of the file src/handlers/issue-handlers.ts. Such manipulation of the argument state/labels leads to os command injection. The attack can be launched remotely. Upgrading to version 0.4.1 is recommended to address this issue. The name of the patch is 253d93bbdf7ee9fe42bd8fdf15feea93ae59cbae. It is suggested 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-116369?


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

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

## Is CVE-2026-116369 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116369 is a medium-severity vulnerability in Sunwood-ai-labs github-kanban-mcp-server, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116369 in the wild and no public exploit code.

Affected product: Sunwood-ai-labs github-kanban-mcp-server. 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-116369/ (Markdown: https://insights.sbomify.com/CVE-2026-116369/index.md)
```

## Sources

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

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