KubeAI: OS Command Injection via Model URL in Ollama Engine startup probe allows arbitrary command execution in model pods

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.7 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N

EPSS

• CVE-2026-34940: 0.47% estimated exploitation activity in the next 30 days; percentile 40.35 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

CHAMP: Description Summary The ollamaStartupProbeScript() function in internal/modelcontroller/engineollama.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. Details The parseModelURL() function in internal/modelcontroller/modelsource.go uses a regex (^([a-z0-9]+):\/\/([^?]+)(\?.)?$) to parse model URLs. The ref component (capture group 2) matches [^?]+, allowing any characters except ?, including shell metacharacters like ;, |, $(), and backticks. The ?model= query parameter (modelParam) is also extracted without any sanitization. Vulnerable code (permalink): This script is then used as a bash -c startup probe (permalink): Compare with the vLLM engine which safely passes the model ref as a command-line argument (not…

Published by the source

1 Apr 2026, 23:22 UTC

Last modified by the source

15 Apr 2026, 21:06 UTC

Source last checked

26 Oct 2026, 15:19 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-324q-cwx9-7crr

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-34940

Advisory: KubeAI: OS Command Injection via Model URL in Ollama Engine startup probe allows arbitrary command execution in model pods
IDs: CVE-2026-34940, GHSA-324q-cwx9-7crr
Record: https://patchnext.com/advisories/cve-2026-34940 (revision 1, source checked 26 Oct 2026, 15:19 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/kubeai-project/kubeai 0.23.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/kubeai-project/kubeai: affected <= 0.23.1; fixed in 0.23.2

## Suggested inspection (read-only)
- Go github.com/kubeai-project/kubeai: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/kubeai-project/kubeai.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-324q-cwx9-7crr (GitHub-reviewed advisory GHSA-324q-cwx9-7crr lists affected ranges: Go github.com/kubeai-project/kubeai >=0 <=0.23.1)

Commands are suggestions: review each one before running it.