Credential Exfiltration Vulnerability in n8n: Bypass of Allowed HTTP Request Domains

n8n Updated 19 May 2026

Summary

19/05/2026
MODERATE
Yes i
Moderate
9.1

GHSA-3875-8gcx-7v46: n8n: Credential exfiltration via Allowed HTTP Request Domains Bypass. Affects n8n versions < 2.20.0. Fixed in 2.20.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

n8n is an open-source workflow automation tool that allows users to connect various applications and services to automate tasks. It provides a user-friendly interface for creating workflows and supports a wide range of integrations. However, n8n has a vulnerability that allows authenticated users to bypass restrictions on HTTP request domains, potentially leading to credential exfiltration.

Vulnerability Detail

The vulnerability exists in the POST /rest/dynamic-node-parameters/options endpoint, which permits any authenticated user to make HTTP requests that include sensitive credentials. This bypasses the intended restrictions on which hosts can be contacted using those credentials. The risk is significant as it can lead to unauthorized access to sensitive information, affecting the confidentiality of user data.

How To Fix

Latest published version: 2.44.6 as of 22 Oct 2026

npm install n8n@2.44.6

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.20.0

This is the first release that contains the fix.

npm install n8n@2.20.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If upgrading is not immediately feasible, consider the following temporary mitigations: 1. Restrict access to n8n to fully trusted users only. 2. Limit credential sharing to users who genuinely require access to those credentials. These measures should only be used as short-term solutions.

Conclusion

The credential exfiltration vulnerability in n8n poses a significant risk to users by allowing unauthorized access to sensitive information. It is crucial to upgrade to the patched version 2.20.0 or implement temporary workarounds to mitigate the risk. Continuous monitoring with tools like Vulert can help maintain security.

See every vulnerability recorded for n8n →

Share this vulnerability

FAQ

The vulnerability allows authenticated users to bypass restrictions on HTTP request domains, potentially leading to credential exfiltration.

The CVSS score of this vulnerability is 9.1, indicating a high level of severity.

Implement temporary workarounds such as restricting access to trusted users and limiting credential sharing.

Detailed information can be found in the official advisory on GitHub or by using Vulert to monitor your application.

Vulert monitors and alerts in real-time for open-source vulnerabilities using just the package-lock.json file, allowing you to check if your application is affected.

Related vulnerabilities

Recent vulnerabilities recorded for n8n.

How To Fix

Latest published version: 2.44.6 as of 22 Oct 2026

npm install n8n@2.44.6

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.20.0

This is the first release that contains the fix.

npm install n8n@2.20.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback