CVE-2026-77075 is a high severity (7.3) expression injection in n8n's editor. A stored value in a resource locator field is evaluated as JavaScript in another user's session when they open the node. n8n before 1.123.69, 2.33.4 and 2.34.1 is affected. Upgrade to those versions or later.
What's affected
The record says n8n before 1.123.69, 2.x before 2.33.4, and 2.34.x before 2.34.1 are affected. GitHub's advisory lists the same range and says the patched versions are 1.123.69, 2.33.4 and 2.34.1 or later.
The component is the link preview for resource locator fields. An authenticated member stores a crafted value, and when another user opens the affected node in the editor, the expression runs as JavaScript in the victim's authenticated session.
Where sources differ. The advisory scores this High 8.4 on CVSS 4.0, and the record's CVSS 3.1 score is different, so the two numbers describe the same flaw through different scoring models.
How to check if you're exposed
Find every n8n instance, including ones a team stood up on its own, and print the version:
n8n --version
docker exec <container> n8n --version
npm ls -g n8n
The first works where the CLI is installed, the second for a Docker container, the third for a global npm install. Compare with the patched versions: 1.123.69 on the 1.x line, 2.33.4 on 2.33, and 2.34.1 on 2.34. Review which users can share or import workflows, since those are the delivery routes.
GitHub lists these temporary mitigations in the advisory:
- Restrict n8n instance access to fully trusted users only.
- Disable workflow import from file or URL to reduce the delivery surface on community edition deployments.
- On instances with workflow sharing enabled, restrict sharing permissions to fully trusted users only.
GitHub is clear that they do not fully remediate the risk and are short-term measures. A dependency scan is the quickest way to find this kind of component across many projects. Safeguard's free in-browser scan at gold.safeguard.sh/scan checks your dependencies against known CVEs, and reachability analysis helps you separate libraries your code actually calls from ones that only sit in the tree.
What to do now
- Upgrade n8n to 1.123.69, 2.33.4, or 2.34.1 or later, whichever matches your release line.
- Until you can, apply the advisory's temporary mitigations, which GitHub says reduce risk without fully fixing it.
- Review who has accounts on the instance and what role each holds. Remove people who do not need access.
- Look through existing workflows for the feature involved, and confirm nothing unexpected has been added.
- Re-check the version afterward and record it.
Why it matters
When the editor drew the link preview for a resource locator, it placed the stored field value straight into the node type's URL template without checking whether the value held expression syntax. n8n evaluates expressions as JavaScript, so a stored value could run code. The record files this under CWE-94, improper control of generated code.
The attack depends on delivery. A crafted workflow has to reach another user, through sharing or import, and that user has to open the node. That is why the advisory's mitigations center on import and sharing. Cross-user script execution in an editor is serious because the editor session can read and change workflows and credentials. The record does not mark it as a CISA KEV entry.
Quick check
How does an attacker deliver it?
By storing a malicious value in a workflow that another user opens, for example through sharing or import. The advisory's mitigations point at those paths.
Whose session runs the code?
The victim's authenticated session, in the editor.
Sources
Last reviewed: 18 October 2026.
