# CVE-2026-110851: n8n before 2.41.4 and 2.42.1 Cross-Project Agent Ownership Transfer via Agents Create Endpoint

> An authenticated user can bypass authorization checks to transfer ownership of agents from other projects to their own, modifying agent details.

- **Severity:** Medium 6.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:L/SC:L/SI:L/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:** 14 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-2r5r-xgvc-rj4p, GHSA-wrfc-h8h3-x3xj

## What is CVE-2026-110851?

CVE-2026-110851 is a medium-severity missing authorization vulnerability in n8n-io n8n, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

n8n before 2.41.4 and 2.42.x before 2.42.1 contains an authorization bypass in the Agents create endpoint, which accepts a caller-supplied Agent ID, checks permissions only against the requested project, and updates an existing Agent without verifying which project owns it. An authenticated user with read-only Agent access to another project can supply an existing Agent ID to move that Agent into their own project and rewrite its name, schema and version.

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

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


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

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

## Is CVE-2026-110851 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110851 is a medium-severity missing authorization vulnerability in n8n-io n8n, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-110851 in the wild and no public exploit code.

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

## Sources

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

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