# CVE-2026-111605: Jpom through 2.11.12 Cross-Workspace Authorization Bypass via SshFileController

> Authenticated users can bypass workspace isolation to read, modify, or delete files on SSH hosts belonging to other workspaces.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-cr5j-j45g-7pmc

## What is CVE-2026-111605?

CVE-2026-111605 is a high-severity missing authorization vulnerability in dromara Jpom, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jpom through 2.11.12 contains an authorization bypass vulnerability in SshFileController that allows authenticated workspace users to access SSH hosts belonging to other workspaces by supplying foreign SSH asset ids. Attackers with SSH file permissions in any workspace can call download, upload, read_file_data.json, update_file_data.json, delete.json, rename.json and new_file_folder.json endpoints to read, modify and delete files on other workspaces' SSH hosts.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-111605 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111605 is a high-severity missing authorization vulnerability in dromara Jpom, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111605 exists.

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

## Sources

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

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