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

> Remote attackers can execute arbitrary commands on Jaaz servers via crafted network requests, leading to full system compromise.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Apr 2026
- **Updated:** 15 Apr 2026
- **Also known as:** GHSA-q3rq-78c6-33vh

## What is CVE-2026-30616?

CVE-2026-30616 is a high-severity command injection vulnerability in n/a, published on 15 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Jaaz 1.0.30 contains a remote code execution vulnerability in its MCP STDIO command execution handling. A remote attacker can send crafted network requests to the network-accessible Jaaz application, causing attacker-controlled commands to be executed on the server. Successful exploitation results in arbitrary command execution within the context of the Jaaz service, potentially allowing full compromise of the affected system.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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


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

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

## Is CVE-2026-30616 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-30616 is a high-severity command injection vulnerability in n/a, published on 15 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-30616 in the wild and no public exploit code.

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-30616/ (Markdown: https://insights.sbomify.com/CVE-2026-30616/index.md)
```

## Sources

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

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