# CVE-2026-108595: Phi 0.3.0 through 0.28.4 Permission Bypass via agent_spawn Workdir

> Attackers can bypass workspace restrictions in Phi to write files anywhere via prompt injection, requiring an upgrade to secure the agent spawn mechanism.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:H/VA:N/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:** 10 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-x8rp-9mrq-5584

## What is CVE-2026-108595?

CVE-2026-108595 is a medium-severity missing authorization vulnerability in pulseaiclub phi, published on 10 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

Phi 0.3.0 through 0.28.4 contains a permission bypass vulnerability that allows spawned sub-agents to escape workspace_only_writes and readonly mode by supplying an unchecked workdir to agent_spawn. Attackers can plant prompt-injected instructions in processed content so the agent spawns a worker rooted elsewhere, causing unapproved file writes anywhere the user can write.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-108595 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108595 is a medium-severity missing authorization vulnerability in pulseaiclub phi, published on 10 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-108595 exists.

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

## Sources

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

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