Skip to main content
CVE-2025-62726VulnerabilityPublished Updated

CVE-2025-62726: n8n · Untrusted Functionality Inclusion

Affects n8nSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High : upgrade to 1.113.0 soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.113.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Upgrade n8n-io/n8n to 1.113.0.

Affected software

ProductAffectedFixed in
npmn8n-io/n8npkg:npm/n8n-io/n8nOther threatsAffected
  • <1.113.0
Fixed in
  • 1.113.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately upgrade all n8n instances to version 1.113.0 or later to remediate this vulnerability. Until patching is complete, restrict network access to the Git Node component and limit the ability to clone repositories from untrusted sources. Implement strict repository whitelisting and code review policies to prevent malicious Git hooks from entering the environment. Employ runtime application monitoring to detect anomalous process executions indicative of hook-triggered code execution. Use least privilege principles for n8n service accounts to minimize the impact of potential exploitation. Regularly audit workflows and connected credentials for unauthorized changes. Additionally, segregate n8n environments from critical infrastructure to contain potential breaches. Finally, maintain up-to-date backups of workflows and configurations to enable rapid recovery if compromise occurs.

Description

n8n is an open source workflow automation platform. Prior to 1.113.0, a remote code execution vulnerability exists in the Git Node component available in both Cloud and Self-Hosted versions of n8n. When a malicious actor clones a remote repository containing a pre-commit hook, the subsequent use of the Commit operation in the Git Node can inadvertently trigger the hook’s execution. This allows attackers to execute arbitrary code within the n8n environment, potentially compromising the system and any connected credentials or workflows. This vulnerability is fixed in 1.113.0.

References

Community reviews

Loading reviews…