Skip to main content
← Vulnerabilities

Jan 0.8.5 before 0.8.8 Workspace Guard Bypass via Dangling Symlink

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

5.7MediumCNA
Exploited
No known exploitation
Fix
Fixed in 0.8.8
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 0.8.8.

6Pcve.now Index 6 of 100 · methodology v3 · provisional
  • Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
  • Exposure?/25Exposure: unknown (data gap). No advisory context yet
  • Reach?/20Reach: unknown (data gap). No tracked technology or package matched
  • Severity5.7/10CVSS 5.7
  • No patch0/5No signal

What would change the score

  • Would score about 61 if added to CISA KEV
  • Would score about 56 if CISA's SSVC rates exploitation active
  • Would score about 28 if advisories confirm default setups are exposed

CVE-2026-122235 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.7 (medium) and affects jan; fixed in 0.8.8.

Published
Last modified
Published
Not listed in CISA KEV
6/100 · provisional
Fix
Fixed in 0.8.8
None on Exploit-DB, Metasploit or GitHub

Summary

Jan, an AI assistant application, from 0.8.5 before 0.8.8 has a workspace guard bypass in its agent tools that lets a local attacker write files outside the workspace by following dangling symlinks, which can lead to changes such as planting an authorized_keys file in a user's home directory. Exploitation requires the victim to take an action, such as opening a malicious repository and having the agent process its prompts.

Read the original 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.

What to do

  • Upgrade to a fixed version: 0.8.8.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • janhq jan

    From 0.8.5 · fixed in 0.8.8

Evidence 5

  1. Advisory
  2. Patch
  3. Patch
  4. Repository
  5. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-122235

Is CVE-2026-122235 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-122235?

jan: from 0.8.5 before 0.8.8.Source: cve.now feed data

How do I fix CVE-2026-122235?

Upgrade to a fixed version: 0.8.8.Source: cve.now feed data