# CVE-2026-34940: KubeAI: OS Command Injection via Model URL in Ollama Engine startup probe allows arbitrary command execution in model pods

> Attackers can execute arbitrary shell commands in model pods by injecting malicious URLs into KubeAI Model resources.

- **Severity:** High 8.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Apr 2026
- **Updated:** 16 Apr 2026
- **Also known as:** GHSA-324q-cwx9-7crr, GO-2026-4920

## What is CVE-2026-34940?

CVE-2026-34940 is a high-severity command injection vulnerability in kubeai-project kubeai, published on 6 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

KubeAI is an AI inference operator for kubernetes. Prior to 0.23.2, the ollamaStartupProbeScript() function in internal/modelcontroller/engine_ollama.go constructs a shell command string using fmt.Sprintf with unsanitized model URL components (ref, modelParam). This shell command is executed via bash -c as a Kubernetes startup probe. An attacker who can create or update Model custom resources can inject arbitrary shell commands that execute inside model server pods. This vulnerability is fixed in 0.23.2.

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

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

3 open source packages ship an affected version, including github.com/kubeai-project/kubeai. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/kubeai-project/kubeai` | Go | All versions | 0.23.2 |
| `github.com/kubeai-project/kubeai` | Go | All versions | 0.23.2 |
| `github.com/kubeai-project/kubeai` | Go | All versions | 0.23.2 |

Products: Kubeai Kubeai.

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

Upgrade github.com/kubeai-project/kubeai to 0.23.2 or later.

## Is CVE-2026-34940 being exploited?

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

Public exploit code:

- OS command injection in KubeAI via an Ollama model URL — CVE-2026-34940 / CVSS 8.7 (github_poc): https://github.com/romain-deperne/CVE-2026-34940

## Fix prompt for AI coding agents

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

What it is: CVE-2026-34940 is a high-severity command injection vulnerability in kubeai-project kubeai, published on 6 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34940 exists.

Affected packages and fixed versions:
- github.com/kubeai-project/kubeai (Go): affected all versions; fixed in 0.23.2
- github.com/kubeai-project/kubeai (Go): affected all versions; fixed in 0.23.2
- github.com/kubeai-project/kubeai (Go): affected all versions; fixed in 0.23.2

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

## Sources

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

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