# CVE-2026-122235: Jan 0.8.5 before 0.8.8 Workspace Guard Bypass via Dangling Symlink


- **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
- **Fix available:** No
- **Published:** 4 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-7j4g-mj5j-p842, GHSA-pjpc-p955-xv4f

## What is CVE-2026-122235?

CVE-2026-122235 is a medium-severity vulnerability in janhq jan, published on 4 Nov 2026. 

### Official description

Jan from 0.8.5 before 0.8.8 contains a workspace guard bypass vulnerability in the agent-tools gate.rs that allows attackers to write files outside the workspace via dangling symlinks. Attackers supplying a malicious repository can use prompt injection to make the write or edit tools follow symlinks, creating files like ~/.ssh/authorized_keys on the host.

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

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


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

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

## Is CVE-2026-122235 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-122235 is a medium-severity vulnerability in janhq jan, published on 4 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-122235 in the wild and no public exploit code.

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

## Sources

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

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