Skip to main content
CVE-2026-25631VulnerabilityPublished

CVE-2026-25631: n8n · Improper Input Validation

Affects n8nSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.121.0 when convenient.

Data as of 26 Oct 2026, 08:30 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Feb 2026

  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 26 Oct 2026.

What to do

Upgrade n8n and n8n-io/n8n to 1.121.0.

Affected software

ProductAffectedFixed in
n8n-ion8nAffected
  • <1.121.0
Fixed in
  • 1.121.0
GitHubn8n-io/n8npkg:github/n8n-io/n8nOther threatsAffected
  • <1.121.0
Fixed in
  • 1.121.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 all n8n instances to version 1.121.0 or later immediately to apply the official fix. 2. Review and audit all credential configurations in n8n, particularly those using wildcard domain patterns in the "Allowed domains" setting. Replace wildcard entries with explicit domain names wherever feasible to reduce the attack surface. 3. Implement strict access controls and multi-factor authentication (MFA) for n8n user accounts to minimize the risk of attacker authentication. 4. Monitor n8n logs for unusual HTTP request patterns or attempts to send credentials to unexpected domains. 5. Segment n8n infrastructure within the network to limit exposure and restrict outbound traffic to only trusted domains. 6. Educate administrators and users about the risks of wildcard domain usage in credential settings and enforce secure configuration policies. 7. Regularly review and update workflow automation security policies to include validation of credential domain restrictions. 8. Consider deploying runtime application self-protection (RASP) or web application firewalls (WAF) that can detect and block anomalous outbound requests from n8n nodes. These steps go beyond generic advice by focusing on configuration hygiene, access control, monitoring, and network segmentation tailored to the specifics of this vulnerability.

Description

n8n is an open source workflow automation platform. Prior to 1.121.0, there is a vulnerability in the HTTP Request node's credential domain validation allowed an authenticated attacker to send requests with credentials to unintended domains, potentially leading to credential exfiltration. This only might affect user who have credentials that use wildcard domain patterns (e.g., *.example.com) in the "Allowed domains" setting. This issue is fixed in version 1.121.0 and later.

References

Community reviews

Loading reviews…