CVE-2025-65964: N8n vulnerability (CVSS 8.8)

Description

n8n is an open source workflow automation platform. Versions 0.123.1 through 1.119.1 do not have adequate protections to prevent RCE through the project's pre-commit hooks. The Add Config operation allows workflows to set arbitrary Git configuration values, including core.hooksPath, which can point to a malicious Git hook that executes arbitrary commands on the n8n host during subsequent Git operations. Exploitation requires the ability to create or modify an n8n workflow using the Git node. This issue is fixed in version 1.119.2. Workarounds include excluding the Git Node (Docs) and avoiding cloning or interacting with untrusted repositories using the Git Node.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredLow

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

N8n≥ 0.123.1 < 1.119.2

Remediation

Fixed in

N8n≥ 1.119.2

Patch & vendor advisories

References

https://github.com/n8n-io/n8n/commit/d5a1171f95f75def5c3ac577707ab913e22aef04Patch
https://github.com/n8n-io/n8n/releases/tag/n8n%401.119.2Release Notes
https://github.com/n8n-io/n8n/security/advisories/GHSA-wpqc-h9wp-chmqExploitVendor Advisory
https://n8n-docs.teamlab.info/hosting/securing/blocking-nodes/#exclude-nodesThird Party Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2025-65964 being actively exploited?

CVE-2025-65964 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.66%.

How severe is CVE-2025-65964?

CVE-2025-65964 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 0.66% probability of exploitation.

Which products are affected by CVE-2025-65964?

Affected products include N8n.

How do I fix CVE-2025-65964?

Upgrade affected software to a fixed version, for example N8n 1.119.2 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-65964 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo