# CVE-2026-103247: n8n before 1.123.80 Credential Tampering via Duplicate Node IDs

> Attackers with editor access can bypass credential tamper guards via duplicate node IDs to steal secrets and redirect them to attacker-controlled hosts.

- **Severity:** Medium 5.8 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:H/SI:H/SA:H`)
- **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:** 1 Oct 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-7gjv-rcf8-x5qc, GHSA-v9vf-c827-9m93

## What is CVE-2026-103247?

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

### Official description

n8n versions before 1.123.80 contain a credential tampering vulnerability where duplicate node IDs bypass the workflow credential tamper guard. Attackers with editor access to shared workflows can exploit mismatched node ID and name matching to retain victim credentials and redirect secrets to attacker-controlled hosts.

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

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


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

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

## Is CVE-2026-103247 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-103247 is a medium-severity vulnerability in n8n-io n8n, published on 1 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-103247 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-103247/ (Markdown: https://insights.sbomify.com/CVE-2026-103247/index.md)
```

## Sources

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

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