HomeVulnerabilityVital n8n flaws disclosed together with public exploits

Vital n8n flaws disclosed together with public exploits

A number of essential vulnerabilities within the common n8n open-source workflow automation platform permit escaping the confines of the surroundings and taking full management of the host server.

Collectively tracked as CVE-2026-25049, the problems might be exploited by any authenticated person who can create or edit workflows on the platform to carry out unrestricted distant code execution on the n8n server.

Researchers at a number of cybersecurity firms reported the issues, which stem from n8n’s sanitization mechanism and bypass the patch for CVE-2025-68613, one other essential flaw addressed on December 20.

Wiz

In line with Pillar Safety, exploiting CVE-2026-25049 allows full compromise of the n8n occasion and could possibly be leveraged to run arbitrary system instructions on the server, steal all saved credentials, secrets and techniques (API keys, OAuth tokens), and delicate configuration information.

By exploiting the vulnerability, the researchers have been additionally capable of entry the filesystem and inside techniques, pivot to related cloud accounts, and hijack AI workflows (intercept prompts, modify responses, redirect visitors).

As n8n is a multi-tenant surroundings, accessing inside cluster companies can doubtlessly permit pivoting to different tenants’ knowledge.

See also  New "GoFetch" Vulnerability in Apple M-Collection Chips Leaks Secret Encryption Keys

“The assault requires nothing particular. If you happen to can create a workflow, you’ll be able to personal the server,” Pillar Safety says in a report as we speak.

Full attack chain
Full assault chain
Supply: Pillar Safety

Pillar’s report describes the issue as incomplete AST-based sandboxing and explains that it arises from n8n’s weak sandboxing of user-written server-side JavaScript expressions in workflows.

On December 21, 2025, they demonstrated a chained bypass to the n8n crew, permitting sandbox escape and entry to the Node.js international object, resulting in RCE.

A repair was applied two days later, however upon additional evaluation, Pillar discovered it incomplete, and a second escape through a distinct mechanism utilizing equal operations remained potential.

n8n builders confirmed the bypass on December 30, and finally, n8n launched model 2.4.0 on January 12, 2026, addressing the problem.

Researchers at Endor Labs additionally found sanitization bypasses and demonstrated the CVE-2026-25049 vulnerability with a easy proof-of-concept (PoC) exploit that achieves distant code execution.

“In all variations previous to 2.5.2 and 1.123.17, the sanitization operate assumes keys in property accesses are strings in attacker-controlled code,” says Cristian Staicu of Endor Labs.

See also  Agentic AI already hinting at cybersecurity’s pending id disaster

Nonetheless, whereas the test is mirrored in TypeScript typings, it’s not enforced at runtime, introducing a type-confusion vulnerability. This results in bypassing the “sanitization controls fully, enabling arbitrary code execution assaults.”

In a report as we speak, researchers at SecureLayer7 present the technical particulars that enabled them to obtain “server facet JavaScript execution utilizing the Operate constructor.”

They found CVE-2026-25049 whereas analyzing CVE-2025-68613 and n8n’s repair for it. It took greater than 150 failed makes an attempt to refine a profitable bypass.

SecureLayer7’s report additionally features a PoC exploit and detailed steps for the preliminary setup and making a malicious workflow that results in full server management.

Beneficial steps

n8n customers ought to replace the platform to the latest model (at the moment 1.123.17 and a couple of.5.2). Pillar security additionally recommends rotating the ‘N8N_ENCRYPTION_KEY’ and all credentials saved on the server, and reviewing workflows for suspicious expressions.

If updating will not be potential for the time being, the n8n crew gives directors with a workaround, which acts as a short lived mitigation and doesn’t fully deal with the danger:

  • Restrict workflow creation and modifying permissions to totally trusted customers solely
  • Deploy n8n in a hardened surroundings with restricted working system privileges and community entry to cut back the impression of potential exploitation
See also  AWS Patches Essential 'FlowFixation' Bug in Airflow Service to Stop Session Hijacking

Presently, there haven’t been any public studies about CVE-2026-25049 being exploited. Nonetheless, n8n’s rising reputation seems to have caught the eye of cybercriminals within the context of the Ni8mare flaw (CVE-2026-21858).

GreyNoise this week reported seeing doubtlessly malicious exercise concentrating on uncovered n8n endpoints weak to Ni8mare, logging at the least 33,000 requests between January 27 and February 3.

Though this probing could possibly be on account of analysis exercise, scanning for the /proc filesystem signifies curiosity in post-exploitation potential.

tines

Trendy IT infrastructure strikes quicker than handbook workflows can deal with.

On this new Tines information, find out how your crew can scale back hidden handbook delays, enhance reliability by way of automated response, and construct and scale clever workflows on prime of instruments you already use.

- Advertisment -spot_img
RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

- Advertisment -

Most Popular