# CVE-2026-110853: n8n before 1.123.83 Authorization Bypass via Execute Sub-workflow Inline JSON

> Authenticated users can bypass authorization to access credentials and modify data in other projects via workflow identity spoofing.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:H/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:** 16 Oct 2026
- **Also known as:** GHSA-866p-xg8v-g2q7, GHSA-9mgf-2q6c-j3gw

## What is CVE-2026-110853?

CVE-2026-110853 is a high-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 1.123.83 contains an authorization bypass vulnerability that allows authenticated members to spoof workflow identity by supplying a trusted identifier in Execute Sub-workflow inline JSON mode. Attackers can set this identifier to resolve credentials from projects they do not belong to and modify another workflow's static data and error-workflow dispatch.

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

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


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

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

## Is CVE-2026-110853 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110853 is a high-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-110853 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-110853/ (Markdown: https://insights.sbomify.com/CVE-2026-110853/index.md)
```

## Sources

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

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