CVE-2026-21877
criticalpriority · track · 12EPSS 0.054 · 93 %ileexploit · PoCDEEURUUSEPSS · scored 2026-10-27
n8n is an open source workflow automation platform. In versions 0.121.2 and below, an authenticated attacker may be able to execute malicious code using the n8n service. This could result in full compromise and can impact both self-hosted and n8n Cloud instances. This issue is fixed in version 1.121.3. Administrators can reduce exposure by disabling the Git node and limiting access for untrusted users, but upgrading to the latest version is recommended.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
exploits (2)
Public proof-of-concept and weaponised exploit code.
- CVEs-Labs/CVE-2026-21877CVEs-Labs/CVE-2026-21877PoC · poc_in_github
- monkeontheroof/cve-2026-21877-rcemonkeontheroof/cve-2026-21877-rcePoC · poc_in_github
affected products (6)
Products and version ranges known to be affected.
advisories (2)
Vendor and ecosystem advisories describing this.
- WID-SEC-W-2026-0025n8n: Schwachstelle ermöglicht CodeausführungDeutsch2026-01-06csaf · cert_bundDE
Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in n8n ausnutzen, um beliebigen Programmcode auszuführen.
- GHSA-v364-rw7m-3263n8n Vulnerable to RCE via Arbitrary File Write2026-01-06ghsa · osvUS
### Impact n8n is affected by an authenticated Remote Code Execution (RCE) vulnerability. Under certain conditions, an authenticated user may be able to cause untrusted code to be executed by the n8n service. This could result in full compromise of the affected instance. Both self-hosted and n8n Cloud instances are impacted. ### Patches The issue has been resolved in n8n version 1.121.3. Users are advised to upgrade to this version or later to fully address the vulnerability. ### Workarounds If upgrading is not immediately possible, administrators can reduce exposure by disabling the Git node and limiting access for untrusted users. ### References - n8n documentation: [Blocking access to nodes](https://docs.n8n.io/hosting/securing/blocking-nodes/)
also known as (5)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (7)
External citations — patches, advisories, analysis.
- https://github.com/n8n-io/n8n/commit/f4b009d00d1f4ba9359b8e8f1c071e3d910a55f6cnnvd
- https://github.com/n8n-io/n8n/releasesPatchcnnvd
- https://github.com/n8n-io/n8n/security/advisories/GHSA-v364-rw7m-3263cnnvd
- https://github.com/n8n-io/n8n/commit/f4b009d00d1f4ba9359b8e8f1c071e3d910a55f6enisa_euvd
- https://github.com/n8n-io/n8n/security/advisories/GHSA-v364-rw7m-3263enisa_euvd
- https://github.com/n8n-io/n8n/commit/f4b009d00d1f4ba9359b8e8f1c071e3d910a55f6Patchnvd
- https://github.com/n8n-io/n8n/security/advisories/GHSA-v364-rw7m-3263Vendor Advisorynvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan