# CVE-2026-102697: Ollama 0.14.0 before 0.31.2 Experimental Agent Bash Approval Bypass via Prefix-Based Authorization

> Attackers can bypass Bash command approval in Ollama's experimental agent mode via prompt injection, leading to arbitrary code execution.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 29 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-44m8-pr79-3734, MINI-7q5q-rpf5-jxx3, MINI-pc59-mm3q-j6p8

## What is CVE-2026-102697?

CVE-2026-102697 is a high-severity vulnerability in ollama, published on 29 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Ollama versions 0.14.0 before 0.31.2 contain an incorrect authorization vulnerability in the experimental agent mode Bash tool approval mechanism that fails to properly parse shell syntax. Attackers who can influence model output through prompt injection can execute additional shell commands by appending control operators like semicolons or logical operators to approved commands, bypassing the session approval requirement.

Weakness: CWE-863 (Incorrect Authorization)

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


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

Upgrade to a fixed version.

## Is CVE-2026-102697 being exploited?

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

Public exploit code:

- BlindLlama: CVE-2026-102697 Reproduction (github_poc): https://github.com/akinerkisa/blindllama-cve-2026-102697

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102697 is a high-severity vulnerability in ollama, published on 29 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-102697 in the wild and no public exploit code.

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

## Sources

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

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