n8n's domain allowlist bypass enables credential exfiltration
CVE-2026-25631 · GHSA-2xcx-75h9-vr9h · published 2026-02-04 · updated 2026-02-19
- Severity
- Medium
- CVSS score
- 5.3
- Chance of exploitation (EPSS)
- 0.30%
- Fixed in
- 1.121.0
- Exploitation No known exploitation
- Automatable No
- Technical impact Partial
- CISA SSVC
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.
Upgrade n8n to 1.121.0 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
This issue is fixed in version 1.121.0 and later. All users are strongly encouraged to upgrade.
Until projects can upgrade: Replace wildcard domain patterns with explicit domain listings in HTTP Request credentials Review and restrict workflow creation/modification permissions to trusted users only Audit existing workflows using HTTP Request nodes with domain-restricted credentials n8n has adopted CVSS 4.0 as primary score for all security advisories. CVSS 3.1 vector strings are provided for backward compatibility. CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| n8n | npm | < 1.121.0 | 1.121.0 |
- CriticalPhoenix: Format String Injection in applyChatTemplatearize-phoenix
- CriticalFlowise: Unauthenticated OAuth2 token refresh endpoint returns access tokens — enables token theft for any connected serviceflowise
- CriticalMLflow: Environment variable injection in AI Gateway secrets enables server-side credential exfiltrationmlflow
- CriticalvLLM has RCE In Video Processingvllm
- HighConfig revision hashes could expose password verifiersopenclaw
- HighWorkspace dotenv files could override provider credentialsopenclaw
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- Criticaln8n Has an Arbitrary File Read via Git Noden8n, n8n, n8n
- Criticaln8n: HTTP Request Node Pagination Prototype Pollution to RCEn8n, n8n, n8n
- Criticaln8n Has an XML Node Prototype Pollution Patch Bypassn8n, n8n, n8n
- Criticaln8n has XML Node Prototype Pollution that to RCEn8n, n8n, n8n
- Criticaln8n has Prototype Pollution in XML Webhook Body Parser that Leads to RCEn8n, n8n, n8n
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.