BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-68613High confidence

n8n Improper Control of Dynamically-Managed Code Resources Vulnerability

n8n · n8n

Official source article: GitHub GHSA-V98V-FF95-F3CP ↗. Check the applicable product and release in the original source.

10.0CriticalCVSS 3.1
Recommended action
Patch now

CISA confirms exploitation in the wild and lists 2026-03-25 as the remediation due date.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • CISA confirms exploitation in the wild.
  • A structured source references public exploit or proof-of-concept material.
  • EPSS is 98.99% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs n8n n8n and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Open-source package ranges2 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
npmn8n>= 0.211.0, < 1.120.41.120.4GitHub advisory ↗upstream repository advisory · 11 Mar 2026
npmn8n>= 1.121.0, < 1.121.11.121.1GitHub advisory ↗upstream repository advisory · 11 Mar 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-204618

CISA KEV mirrored by ENISA

n8n is an open source workflow automation platform. Versions starting with 0.211.0 and prior to 1.120.4, 1.121.1, and 1.122.0 contain a critical Remote Code Execution (RCE) vulnerability in their workflow expression evaluation system. Under certain conditions, expressions supplied by authenticated users during workflow configuration may be evaluated in an execution context that is not sufficiently isolated from the underlying runtime. An authenticated attacker could abuse this behavior to execute arbitrary code with the privileges of the n8n process. Successful exploitation may lead to full compromise of the affected instance, including unauthorized access to sensitive data, modification of workflows, and execution of system-level operations. This issue has been fixed in versions 1.120.4, 1.121.1, and 1.122.0. Users are strongly advised to upgrade to a patched version, which introduces additional safeguards to restrict expression evaluation. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only; and/or deploy n8n in a hardened environment with restricted operating system privileges and network access to reduce the impact of potential exploitation. These workarounds do not fully eliminate the risk and should only be used as short-term measures.

EUVD state
Present in the current official mapping
Known exploitation
Recorded by ENISA since 11 Mar 2026. Evidence sources: cisa_kev.
ENISA score
10.0 · CVSS 3.1
Advisory evidence
1 linked advisory record
Recommended actionPatch now

CISA confirms exploitation in the wild and lists 2026-03-25 as the remediation due date.

Patch available
01

What, why and how

n8n contains an improper control of dynamically managed code resources vulnerability in its workflow expression evaluation system that allows for remote code execution.

What

n8n contains an improper control of dynamically managed code resources vulnerability in its workflow expression evaluation system that allows for remote code execution.

Why

The product does not properly restrict reading from or writing to dynamically-managed code resources such as variables, objects, classes, attributes, functions, or executable instructions or statements.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may execute code or commands in the affected security context.

What

n8n contains an improper control of dynamically managed code resources vulnerability in its workflow expression evaluation system that allows for remote code execution.

Why

The product does not properly restrict reading from or writing to dynamically-managed code resources such as variables, objects, classes, attributes, functions, or executable instructions or statements.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may execute code or commands in the affected security context.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Confirmed in the wild

CISA added this CVE to its Known Exploited Vulnerabilities catalogue on 2026-03-11.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Improper Control of Dynamically-Managed Code Resources → execute code or commands in the affected security context
Attack surface
Network
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-913 ↗

CWE-913: Improper Control of Dynamically-Managed Code Resources. The product does not properly restrict reading from or writing to dynamically-managed code resources such as variables, objects, classes, attributes, functions, or executable instructions or statements.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
NetworkRemote code executionCWE-913CISA KEVPublic exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2025-204618Known-exploited evidence recorded

n8n is an open source workflow automation platform. Versions starting with 0.211.0 and prior to 1.120.4, 1.121.1, and 1.122.0 contain a critical Remote Code Execution (RCE) vulnerability in their workflow expression evaluation system. Under certain conditions, expressions supplied by authenticated users during workflow configuration may be evaluated in an execution context that is not sufficiently isolated from the underlying runtime. An authenticated attacker could abuse this behavior to execute arbitrary code with the privileges of the n8n process. Successful exploitation may lead to full compromise of the affected instance, including unauthorized access to sensitive data, modification of workflows, and execution of system-level operations. This issue has been fixed in versions 1.120.4, 1.121.1, and 1.122.0. Users are strongly advised to upgrade to a patched version, which introduces additional safeguards to restrict expression evaluation. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only; and/or deploy n8n in a hardened environment with restricted operating system privileges and network access to reduce the impact of potential exploitation. These workarounds do not fully eliminate the risk and should only be used as short-term measures.

Official EUVD record ↗
BSI · German · WID-SEC-2026-0040n8n: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in n8n ausnutzen, um beliebigen Programmcode auszuführen, vertrauliche Informationen offenzulegen und Sicherheitsmaßnahmen zu umgehen.

Official advisory ↗
Canadian Centre for Cyber Security · English · AV26-091n8n security advisory (AV26-091)

On February 4, 2026, n8n published security updates to address critical vulnerabilities in the following products:

Official advisory ↗
Canadian Centre for Cyber Security · English · AL26-001AL26-001 – Vulnerabilities affecting n8n – CVE-2026-21858, CVE-2026-21877 and CVE-2025-68613

An Alert is used to raise awareness of a recently identified cyber threat that may impact cyber information assets, and to provide additional detection and mitigation advice to recipients. The Canadian Centre for Cyber Security ("Cyber Centre") is also available to provide additional assistance regarding the content of this Alert to recipients as requested.

Official advisory ↗
Canadian Centre for Cyber Security · English · AV25-857n8n security advisory (AV25-857) – Update 1

On December 19, 2025, n8n published a security update to address a critical vulnerability in the following product: On March 11, 2026, Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2025-68613 to their Known Exploited Vulnerabilities (KEV) Database.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20251224Security Bulletin 24 Dec 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 24 Dec 2025, published on 24 December 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-023704n8nにおける動的に操作されるコードリソースの不適切な制御に関する脆弱性

n8nはオープンソースのワークフロー自動化プラットフォームです。バージョン0.211.0以降、1.120.4、1.121.1、1.122.0より前のバージョンには、ワークフローの式評価システムに深刻なリモートコード実行（RCE）の脆弱性が存在します。特定の状況下で、認証済みユーザーがワークフロー構成時に指定した式が、基盤となるランタイムから十分に隔離されていない実行コンテキストで評価される可能性があります。認証された攻撃者は、この動作を悪用してn8nプロセスの権限で任意のコードを実行できます。攻撃が成功すると、影響を受けるインスタンスが完全に侵害され、機密データへの不正アクセスやワークフローの変更、システムレベルの操作の実行などが発生します。この問題はバージョン1.120.4、1.121.1、1.122.0で修正されています。利用者には、式評価を制限する追加の安全策が導入された修正済みバージョンへのアップグレードを強く推奨します。即時のアップグレードが難しい場合は、以下の暫定的な緩和策を検討してください。ワークフローの作成・編集権限を完全に信頼できるユーザーのみに制限すること、またはn8nをOS権限とネットワークアクセスを制限した強化環境で運用し、潜在的な攻撃時の影響を軽減することを推奨します。これらの回避策はリスクを完全に排除するものではなく、一時的な対策としてのみ利用してください。

Official advisory ↗
KISA KrCERT/CC · Korean · KNVD-6725美 CISA 발표 주요 Exploit 정보공유(Update. 2026-03-11)

n8n Improper Control of Dynamically-Managed Code Resources Vulnerability

Official advisory ↗
KISA KrCERT/CC · Korean · KNVD-6654n8n 제품 보안 업데이트 권고

n8n에서 발생하는 원격 코드 실행(RCE) 취약점(CVE-2025-68613) [1][2]

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
n8n: 0.211.0, < 1.120.4, = 1.121.0
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 19 Dec 2025 · Last source change 12 Mar 2026, 03:55 UTC · CWE-913 · Improper Control of Dynamically-Managed Code Resources

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-204618
Product sourceCISA KEV
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: added remediation: github.com/GHSA-v98v-ff95-f3cp; removed remediation: cyber.gc.ca/al26-001-vulnerabilities-affecting-n8n-cve-2026-21858-cve-2026-21877-cve-2025-68613.
    Before
    patch: github.com/08f332015153decdda3c37ad4fcb9f7ba13a7c79 · patch: github.com/1c933358acef527ff61466e53268b41a04be1000 · patch: github.com/39a2d1d60edde89674ca96dcbb3eb076ffff6316 · 2 more references
    After
    patch: github.com/08f332015153decdda3c37ad4fcb9f7ba13a7c79 · patch: github.com/1c933358acef527ff61466e53268b41a04be1000 · patch: github.com/39a2d1d60edde89674ca96dcbb3eb076ffff6316 · 2 more references
    security-advisories@github.com ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    n8n: >= 0.211.0, < 1.120.4, = 1.121.0 · Fixed: The Cyber Centre recommends that organizations upgrade affected instances of n8n to the latest supported version. The table below shows affected and patched versions for each CVE: Affected product CVE Affected versions Patched versions n8n CVE-2025-68613 version 0.211.0 to versions prior to 1.120.4, 1.121.1 and 1.122.0 1.120.4, 1.121.1, and 1.122.0 n8n CVE-2026-21858 version 1.65.0 to versions prior to 1.121.0 1.121.0 n8n CVE-2026-21877 versions prior to 0.121.2 1.121.3 Note: n8n 1.X version will reach end of life (EOL) by beginning of March 2026 Footnote 9 . If patching is not immediately possible, the vendor suggests that users may restrict or disable publicly accessible webhook and form endpoints until upgrading is complete Footnote 10 . In addition, the Cyber Centre strongly recommends that organizations review and implement the Cyber Centre's Top 10 IT Security Actions with an emphasis on the following topics Footnote 11 . Patch operating systems and applications Harden operating systems and applications Isolate web-facing applications Should activity matching the content of this alert be discovered, recipients are encouraged to report via My Cyber Portal , or email contact@cyber.gc.ca .
    After
    n8n: >= 0.211.0, < 1.120.4, = 1.121.0 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    CISA KEV ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    >= 0.211.0, < 1.120.4; = 1.121.0 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    n8n: >= 0.211.0, < 1.120.4, = 1.121.0 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    CNA ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    n8n: >= 0.211.0, < 1.120.4, = 1.121.0 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    n8n: >= 0.211.0, < 1.120.4, = 1.121.0 · Fixed: The Cyber Centre recommends that organizations upgrade affected instances of n8n to the latest supported version. The table below shows affected and patched versions for each CVE: Affected product CVE Affected versions Patched versions n8n CVE-2025-68613 version 0.211.0 to versions prior to 1.120.4, 1.121.1 and 1.122.0 1.120.4, 1.121.1, and 1.122.0 n8n CVE-2026-21858 version 1.65.0 to versions prior to 1.121.0 1.121.0 n8n CVE-2026-21877 versions prior to 0.121.2 1.121.3 Note: n8n 1.X version will reach end of life (EOL) by beginning of March 2026 Footnote 9 . If patching is not immediately possible, the vendor suggests that users may restrict or disable publicly accessible webhook and form endpoints until upgrading is complete Footnote 10 . In addition, the Cyber Centre strongly recommends that organizations review and implement the Cyber Centre's Top 10 IT Security Actions with an emphasis on the following topics Footnote 11 . Patch operating systems and applications Harden operating systems and applications Isolate web-facing applications Should activity matching the content of this alert be discovered, recipients are encouraged to report via My Cyber Portal , or email contact@cyber.gc.ca .
    Canadian Centre for Cyber Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Added to CISA KEV
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2025-204618↗CISA KEV record↗CVE authority or vendor reference · GitHub GHSA-V98V-FF95-F3CP↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Public exploit reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-68613 · cve.blacktree.nl