# CVE-2026-48547: KanaDojo < 0.1.18 Command Injection via patchNotesData.json in release.yml

> Attackers with pull request access can execute arbitrary shell commands via unsanitized JSON inputs in the release workflow, compromising the CI/CD environment.

- **Severity:** High 8.5 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Jun 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-g3g7-r6qj-455p

## What is CVE-2026-48547?

CVE-2026-48547 is a high-severity command injection vulnerability in lingdojo kana-dojo, published on 11 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

KanaDojo contains a command injection vulnerability that allows an attacker with pull request access to execute arbitrary shell commands by inserting shell metacharacters into the version or changes fields of patchNotesData.json, which are interpolated unsanitized into a child_process.execSync() call in the release.yml workflow. Attackers can have a malicious pull request merged to trigger the GitHub Actions runner with contents write permissions and access to GITHUB_TOKEN.

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

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


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

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

## Is CVE-2026-48547 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-48547 is a high-severity command injection vulnerability in lingdojo kana-dojo, published on 11 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-48547 in the wild and no public exploit code.

Affected product: lingdojo kana-dojo. 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-48547/ (Markdown: https://insights.sbomify.com/CVE-2026-48547/index.md)
```

## Sources

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

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