# CVE-2026-118642: n8n before 1.123.85, 2.43.5, and 2.44.1 Credential Permission Check Bypass via Inline Sub-Workflows


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:H/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-8vrr-mgc5-jg55, GHSA-x95v-p35j-q7f5

## What is CVE-2026-118642?

CVE-2026-118642 is a medium-severity vulnerability in n8n-io n8n, published on 28 Oct 2026. 

### Official description

n8n before 1.123.85, 2.43.5, and 2.44.1 contains an authorization bypass vulnerability that allows authenticated members to use inaccessible credentials through inline sub-workflow nodes with non-boolean disabled values. Attackers knowing a credential id can run Execute Workflow nodes in inline JSON mode that skip the permission check and send decrypted credentials to attacker-controlled servers.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-118642 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-118642 is a medium-severity vulnerability in n8n-io n8n, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-118642 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-118642/ (Markdown: https://insights.sbomify.com/CVE-2026-118642/index.md)
```

## Sources

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

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