# CVE-2026-109560: Continue CLI through 1.5.47 Bash Permission Rule Bypass via Command Chaining

> Attackers can bypass Bash permission rules in Continue CLI by chaining commands, allowing arbitrary code execution as the user.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:P/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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-f54m-g39v-qf2p

## What is CVE-2026-109560?

CVE-2026-109560 is a high-severity vulnerability in continuedev continue, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Continue CLI (@continuedev/cli) through 1.5.47 contains a permission bypass vulnerability that allows attackers to run unapproved commands by chaining them after allowed Bash prefix rules. Attackers can inject instructions into repository files or fetched pages so the agent appends commands after ;, && or | to execute code as the user.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-109560 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109560 is a high-severity vulnerability in continuedev continue, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-109560 exists.

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

## Sources

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

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