Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Medium

n8n HTTP Request node credential domain allowlist bypass

IdentifiersCVE-2026-25631CWE-285

In n8n (open-source workflow automation), versions prior to 1.121.0 contain a flaw in the HTTP Request node’s credential domain validation logic. When credentials are configured with wildcard patterns in the “Allowed domains” setting (e.g., *.example.com), an authenticated attacker can bypass the intended domain restriction and cause the HTTP Request node to send requests to unintended domains while still attaching the stored credentials. This can result in credential exposure/exfiltration to attacker-controlled endpoints. The issue is fixed in n8n 1.121.0 and later.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An authenticated user able to run/modify workflows can coerce n8n into transmitting stored HTTP Request credentials to domains outside the intended allowlist, enabling credential exfiltration and subsequent unauthorized access to external services protected by those credentials. The practical impact is concentrated in environments where credentials rely on wildcard allowed-domain patterns.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible: avoid wildcard patterns in HTTP Request credential “Allowed domains” by using explicit domain entries; restrict workflow creation/modification to fully trusted users; audit existing workflows for HTTP Request nodes that use domain-restricted credentials (especially wildcard patterns) and remediate risky configurations.

Remediation

Patch, then assume compromise.

Upgrade n8n to version 1.121.0 or later, where the HTTP Request node credential domain validation is corrected to prevent unintended-domain use of stored credentials.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
N8nN8napplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity1

Community discussion across Reddit, Mastodon, and other social sources.