Security Flaw in n8n: GraphQL Node Bypasses Allowed HTTP Request Domains Restriction

n8n Updated 23 Jul 2026

Summary

22/07/2026
MODERATE
No i
Moderate
Not published

GHSA-88c4-pcqm-3r9p: Duplicate Advisory: GraphQL Node Bypasses "Allowed HTTP Request Domains" Restriction. Affected versions are not published. No fix is published. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

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 that can integrate APIs, databases, and other services. However, prior to versions 1.123.64, 2.29.8, and 2.30.1, n8n had a vulnerability in its GraphQL node that failed to enforce restrictions on HTTP-based credentials, potentially exposing sensitive information.

Vulnerability Detail

The vulnerability arises from n8n's GraphQL node not enforcing the 'Allowed HTTP Request Domains' restriction on HTTP-based credentials, such as Header Auth, Basic Auth, Query Auth, and OAuth. This oversight allows authenticated users who can create or edit workflows to direct the node's endpoint to a server they control, leading to the exfiltration of restricted credentials. This issue primarily affects instances where credentials are configured with 'Allowed HTTP Request Domains' and are accessible to non-owner users.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, ensure that sensitive credentials are not used in workflows that utilize the GraphQL node until the package is updated. Additionally, restrict access to workflows to only trusted users.

Conclusion

The vulnerability in n8n's GraphQL node poses a significant risk by allowing unauthorized access to sensitive credentials. It is crucial for users to update to the latest versions to mitigate this risk and ensure the security of their workflows.

See every vulnerability recorded for n8n →

Share this vulnerability

FAQ

The vulnerability allows authenticated users to bypass restrictions on HTTP-based credentials in the GraphQL node, potentially leading to credential exfiltration.

Versions of n8n prior to 1.123.64, 2.29.8, and 2.30.1 are affected by this vulnerability.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

As a temporary measure, restrict access to workflows that use the GraphQL node and avoid using sensitive credentials until the package is updated.

Vulert monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json, providing insights into potential security issues in your software.

Related vulnerabilities

Recent vulnerabilities recorded for n8n.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. 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