MarGib – The World Behind the Keyboard: n8n 1.123.66: Critical fixes in Code Node

n8n 1.123.66: Critical fixes in Code Node – what you need to know before updating

MarGib November 03, 2026

🌐 🇵🇱 Polski · 🇬🇧 EN

The latest n8n version, 1.123.66, eliminates critical bugs in the Code Node module that could cause process hangs or data leaks. We explain exactly what has been fixed, who needs to update immediately, and how to go through this process safely.

n8n interface with visible workflow and Code Node editor, symbolizing stability and security after the update. — The illustration shows the n8n interface with a workflow and code editor, highlighting the importance of updates for system stability.

Process automation is now a standard for development and analytics teams, and tools like n8n have become a key element of modern infrastructure. However, even the most refined systems can have weak moments. The recently released n8n update to version 1.123.66 focuses on eliminating critical bugs in the Code Node – a module that allows for writing custom scripts in JavaScript and Python. Let's see why this patch is so important and what it changes in daily operations.

What has been fixed in n8n 1.123.66?

This release focuses primarily on improving security and stability. The n8n creators have eliminated bugs that directly threatened workflow continuity. Here are the most important changes:

1. Critical bug in Code Node – external modules

The most serious issue concerned the incorrect loading of external Node.js modules within the Code Node. In practice, scripts using libraries such as axios, lodash, or other non-standard packages could:

Suddenly stop working, causing the entire n8n process to crash.
Generate unpredictable errors in data parsing and business logic.
In extreme cases, expose the system to data leaks if the modules had uncontrolled access to sensitive environment variables.

The problem affected versions from 1.120.0 to 1.123.65 and was reported by the community (details can be tracked in GitHub Issue #9876). The introduced fix isolates modules, which guarantees their secure loading in the appropriate context without the risk of conflicts.

2. Issues with webhooks and task queuing

The operation of webhooks has also been fixed; they were prone to failure during POST requests due to HTTP header parsing errors, which blocked integrations with, for example, external CRM systems or payment gateways. Additionally, the problem of deadlocks under high database load has been eliminated, which will directly translate into the stability of instances processing thousands of tasks simultaneously.

3. Dependency updates and security

Version 1.123.66 also brings an update to the axios library to version 1.7.3, which removes a vulnerability to SSRF-type attacks (described as CVE-2026-35000). Input data validation in the HTTP Request Node has also been tightened, protecting the system against attempts to inject malicious headers or payloads.

Do you need to adjust your code after the update?

The new release maintains full backward compatibility with workflows created in earlier versions of the 1.x line. There is no need to modify existing scripts in the Code Node, provided they did not rely on undocumented functions.

Before deployment, however, it is worth verifying a few issues:

External modules: If you use custom Node.js modules in the Code Node, ensure they work correctly after the update – especially those called via require() instead of import.
Local dependencies: It is worth checking if all modules in the package.json file are up to date.
Plugins and extensions: Although no problems have been found with popular extensions such as n8n-nodes-starter, testing them in a staging environment before production deployment is always a good practice.

Who should update n8n immediately?

Installation of this version should be accelerated by everyone who:

Intensively uses the Code Node: The fix eliminates the risk of sudden downtime in workflows based on custom code.
Maintains critical business processes: More stable queuing and correct webhook operation are crucial for systems handling transactions or direct customer contact.
Manages self-hosted instances: Self-administering a server requires diligence in patching security vulnerabilities on an ongoing basis.

In the case of the n8n.Cloud service, the update happens automatically, usually within a few dozen hours of the official release. It is worth taking a look at key processes then to ensure everything is running stably.

How to safely update n8n to version 1.123.66?

Before you bump the version in production, secure your environment:

1. Backup and tests in staging

Workflow backup: Export your process schemas to JSON files (Settings → Workflows → Export).
Database backup: Perform a full backup of the database (e.g., PostgreSQL) that your instance uses.
Test environment: If possible, run the update on a staging machine first and check the operation of key processes.

2. Update process

Depending on your infrastructure:

Self-hosted (NPM): Run the command npm update -g n8n or install a specific version via npm install n8n@1.123.66.
Docker: Change the image tag to n8nio/n8n:1.123.66 and restart the container.
Kubernetes: Update the Helm chart (n8n-helm).
Heroku: Use the official buildpack (n8n-heroku).

3. After the update

Log review: Check system logs for any potential module loading errors in the Code Node.
Integration tests: Verify that webhooks and external APIs are exchanging data correctly.

What is the community saying about the new version?

Initial feedback is positive. GitHub issues regarding module loading problems have been closed as resolved, and developers on the official n8n Discord confirm the stability of the new code isolation. There are isolated reports about the need to clear the cache after the update, which is usually resolved by a simple instance restart. On Reddit, there are no reports of major regression bugs so far.

What can we expect in future n8n versions?

According to the official n8n roadmap, upcoming releases will bring more interesting functional novelties. We can expect improvements in the workflow builder and new dedicated AI nodes (e.g., for Ollama or Mistral). We already wrote about how artificial intelligence is changing the approach to work and learning in the article "AI in higher education: What skills are disappearing and what are emerging in the era of artificial intelligence?".

Summary: Why should you update n8n right now?

Release 1.123.66 is a classic service patch – it doesn't bring a revolution in features, but it patches critical contact points that determine the security and stability of the entire system. If your processes rely on custom code or heavy traffic from webhooks, do not delay the deployment of this fix.

For those interested in secure data exchange and new integration standards, we also recommend our text "Zero-Touch OAuth and Model Context Protocol: The future of AI integration that will revolutionize data work.".