# CVE-2026-92588: n8n before 1.123.76 Improper Authorization via Source Control Push

> Authenticated users can delete workflows and credentials from unauthorized projects via the source control push endpoint if the enterprise feature is enabled.

- **Severity:** Medium 5.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Sep 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-cr47-hhfm-v884, GHSA-hvrx-jc5j-pg3w, MINI-hf3c-mfpr-6r92

## What is CVE-2026-92588?

CVE-2026-92588 is a medium-severity missing authorization vulnerability in n8n-io n8n, published on 16 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

n8n is a workflow automation platform. In n8n versions before 1.123.76, 2.37.7, and 2.38.2, the source control push endpoint derived the set of files to push from the file paths and status supplied in the client request payload instead of from the server-side status computed for the requesting user. An authenticated project-scoped user (e.g., a project admin) could therefore reference files belonging to projects they have no access to and push a deletion of those projects' workflows and credentials, resulting in cross-project data destruction. Exploitation requires the Source Control (Environments) enterprise feature to be licensed, enabled, and connected to a remote repository. The issue is fixed in 1.123.76, 2.37.7, and 2.38.2.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-92588 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92588 is a medium-severity missing authorization vulnerability in n8n-io n8n, published on 16 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92588 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-92588/ (Markdown: https://insights.sbomify.com/CVE-2026-92588/index.md)
```

## Sources

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

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