Skip to main content
VulnerabilityPublished

CVE-2026-33724: n8n · Insecure Direct Object Reference

Affects n8nSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium : upgrade to 2.5.0 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.5.0
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 30 Oct 2026.

What to do

Upgrade n8n and n8n-io/n8n to 2.5.0.

Affected software

ProductAffectedFixed in
n8n-ion8nAffected
  • <2.5.0
Fixed in
  • 2.5.0
GitHubn8n-io/n8npkg:github/n8n-io/n8nOther threatsAffected
  • <2.5.0
Fixed in
  • 2.5.0

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

AI-suggested

  1. Upgrade n8n to version 2.5.0 or later immediately, as this version includes the fix that enforces SSH host key verification for Source Control git operations.
  2. If upgrading is not immediately feasible, disable the Source Control feature entirely if it is not actively required to eliminate the attack surface.
  3. Restrict network access so that the n8n instance communicates with the Git server only over trusted, controlled network paths such as VPNs or private networks, minimizing the risk of man-in-the-middle attacks.
  4. Implement network monitoring and intrusion detection systems to detect unusual SSH or git traffic patterns that may indicate interception attempts.
  5. Regularly audit and verify the integrity of workflows and repository contents to detect unauthorized changes promptly.
  6. Educate administrators about the risks of disabling SSH host key verification and encourage strict adherence to secure SSH practices in all automated processes.
  7. Consider deploying SSH bastion hosts or jump servers that enforce strict host key verification policies as intermediaries for git operations. These steps collectively reduce the risk of exploitation and help maintain the integrity and confidentiality of automated workflows.

Description

n8n is an open source workflow automation platform. Prior to version 2.5.0, when the Source Control feature is configured to use SSH, the SSH command used for git operations explicitly disabled host key verification. A network attacker positioned between the n8n instance and the remote Git server could intercept the connection and present a fraudulent host key, potentially injecting malicious content into workflows or intercepting repository data. This issue only affects instances where the Source Control feature has been explicitly enabled and configured to use SSH (non-default). The issue has been fixed in n8n version 2.5.0. Users should upgrade to this version or later to remediate the vulnerability. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Disable the Source Control feature if it is not actively required, and/or restrict network access to ensure the n8n instance communicates with the Git server only over trusted, controlled network paths. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

References

Community reviews

Loading reviews…