CVE-2025-62726: n8n Vulnerable to Remote Code Execution via Git Node Pre-Commit Hook

Published Oct 30, 2025
·
Updated

Impact 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.

All users with workflows that utilize the Git Node to clone untrusted repositories are affected.

Patches The vulnerability was addressed in v1.113.0 (n8n-io/n8n#19559), which introduces a new environment variable: N8NGITNODEDISABLEBAREREPOS. For self-hosted deployments, it is strongly recommended to set this variable to true to mitigate the risk of executing malicious Git hooks.

Workarounds To reduce risk prior to upgrading:

- Avoid cloning or interacting with untrusted repositories using the Git Node. - Disable or restrict the use of the Git Node in workflows where repository content cannot be fully trusted.

Other sources

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.

MITRE

Affected Software

3 affected componentsFixes available
n8n n8n<1.113.0
npm/n8n<1.113.0
1.113.0
n8n N8n Node.js<1.113.0

Event History

Oct 30, 2025
CVE Published
via MITRE·04:24 PM
Data Sourced
via MITRE·04:24 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·05:04 PM
Data Sourced
via GitHub·05:04 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via NVD·05:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:15 PM
RemedyAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-62726?

CVE-2025-62726 is categorized as a critical vulnerability due to the potential for remote code execution.

2

How do I fix CVE-2025-62726?

To mitigate CVE-2025-62726, upgrade n8n to version 1.113.0 or later.

3

What components of n8n are affected by CVE-2025-62726?

CVE-2025-62726 affects the Git Node component in both Cloud and Self-Hosted versions of n8n.

4

Can CVE-2025-62726 be exploited without authentication?

Yes, CVE-2025-62726 can be exploited by unauthenticated users if they clone a malicious repository.

5

What is the impact of CVE-2025-62726 on n8n users?

The impact of CVE-2025-62726 on n8n users is significant, as it allows malicious actors to execute arbitrary code on the server.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203