# CVE-2026-67827: Command injection in n/a

> Remote attackers can execute arbitrary shell commands via unauthenticated access to the setServerConfig API endpoint in ZLMediaKit.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-m78q-27gx-3rwr

## What is CVE-2026-67827?

CVE-2026-67827 is a critical command injection vulnerability in n/a, published on 21 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Incorrect Access Control in the HTTP API module in ZLMediaKit commit 9fd5152 allows remote attackers to achieve Remote Code Execution (RCE) via unauthenticated access to the setServerConfig API endpoint, which permits overwriting the ffmpeg.snap configuration parameter with arbitrary shell commands. These commands are subsequently executed through the getSnap API endpoint with the privileges of the ZLMediaKit process.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2026-67827 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-67827 is a critical command injection vulnerability in n/a, published on 21 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67827 exists.

Affected product: n/a. 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-67827/ (Markdown: https://insights.sbomify.com/CVE-2026-67827/index.md)
```

## Sources

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

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