CVE-2026-25631
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedn8n 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe HTTP Request node in n8n versions prior to 1.121.0 contains a domain validation flaw in credential configuration. When users set wildcard domain patterns (e.g., *.example.com) in the Allowed domains setting, the validation logic can be bypassed, allowing authenticated attackers to send requests with those credentials to unintended domains, potentially exfiltrating sensitive credential data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.121.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check n8n versionRun `n8n --version` or check the version displayed in the n8n UI footerAffected if The installed version is below 1.121.0
-
Identify HTTP Request node credentialsNavigate to Credentials section in n8n UI and filter for credentials that use the HTTP Request nodeAffected if Credentials with HTTP Request node type exist
-
Inspect wildcard domain patternsOpen each HTTP Request credential and examine the Allowed domains field for patterns containing wildcard syntax (e.g., *.example.com)Affected if Allowed domains field contains wildcard patterns like *.domain.com
-
Verify domain validation is enforcedTest creating a new HTTP Request node using the credential and attempt a request to a domain that should be blocked by the wildcard pattern (e.g., if *.example.com is allowed, try sending to random-unintended.com)Affected if Requests to domains outside the intended wildcard scope succeed when they should be blocked
You are affected if running n8n version below 1.121.0 AND have HTTP Request credentials configured with wildcard domain patterns in Allowed domains settings.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.121.0
Upgrade n8n to version 1.121.0 or later. Audit existing credential configurations with wildcard domain patterns to ensure they are properly set and no unauthorized domain access has occurred.
1.121.0
- Upgrade n8n to version 1.121.0 or later
- After upgrading, review credentials that use wildcard domain patterns (e.g., *.example.com) in the 'Allowed domains' setting
- Verify that HTTP Request node credentials are only being used for intended domains
- Check the n8n release notes for 1.121.0 to confirm the security fix is applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25631 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-25631 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data