# CVE-2026-120461: Jpom through 2.11.12 Cross-Workspace Authorization Bypass via /node/ssh_command/batch


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Nov 2026
- **Updated:** 2 Nov 2026
- **Also known as:** GHSA-xxr5-rv8h-2q24

## What is CVE-2026-120461?

CVE-2026-120461 is a high-severity vulnerability in dromara Jpom, published on 2 Nov 2026. 

### Official description

Jpom through 2.11.12 contains a cross-workspace authorization bypass in POST /node/ssh_command/batch that resolves command templates and SSH nodes by ID without workspace filtering. Authenticated users with SSH command execute permission in one workspace can supply foreign template and node IDs to run commands on other workspaces' SSH hosts using their stored credentials.

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

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


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

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

## Is CVE-2026-120461 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120461 is a high-severity vulnerability in dromara Jpom, published on 2 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120461 in the wild and no public exploit code.

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

## Sources

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

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