# CVE-2026-108599: Phi 0.1.1 through 0.28.4 Symlink Workspace Write Restriction Bypass

> Attackers can bypass write restrictions via symlinks and prompt injection to modify external files, affecting users of the Phi AI agent tool.

- **Severity:** Medium 5.7 (`CVSS:4.0/AV:L/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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-mhj6-8rvv-3grj

## What is CVE-2026-108599?

CVE-2026-108599 is a medium-severity path traversal vulnerability in pulseaiclub phi, published on 10 Oct 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

phi 0.1.1 through 0.28.4 contains an improper link resolution vulnerability that allows malicious repositories to bypass workspace_only_writes by exploiting lexical-only path checks in the permission gate. Attackers can commit symlinks pointing outside the workspace and use prompt injection to make the write tool write attacker-influenced content to external files without approval.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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


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

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

## Is CVE-2026-108599 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108599 is a medium-severity path traversal vulnerability in pulseaiclub phi, published on 10 Oct 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-108599 in the wild and no public exploit code.

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

## Sources

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

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