dbcve.org
N8nApplication

CVE-2026-65596

HIGH · 8.1 CVSS v3.1 Published 2026-07-22
Fix available
A fix is available. Upgrade to 1.123.64 / 2.29.8 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click 4 weeks old

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 · unedited
n8n before 1.123.64, 2.29.8, and 2.30.1 fails to enforce the "Allowed HTTP Request Domains" restriction on HTTP-based credentials (Header Auth, Basic Auth, Query Auth, OAuth) in the GraphQL node, unlike the HTTP Request node. An authenticated user able to create or edit workflows can point the node's endpoint at a server they control and exfiltrate restricted credentials. Only instances where a credential has "Allowed HTTP Request Domains" configured and is usable by non-owner users are affected.

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 · moderate confidence

The GraphQL node in n8n fails to enforce the 'Allowed HTTP Request Domains' restriction on HTTP-based credentials (Header Auth, Basic Auth, Query Auth, OAuth), allowing authenticated users with workflow edit permissions to exfiltrate restricted credentials by directing the node to attacker-controlled servers, unlike the HTTP Request node which properly enforces this restriction.

MitigationUpgrade to n8n versions 1.123.64, 2.29.8, or 2.30.1 or later to patch the vulnerability. Additionally, audit credential sharing settings and restrict workflow editing permissions to trusted users until the patch is applied.

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
N8nApplication
Affected:< 1.123.64>= 2.0.0, < 2.29.8= 2.30.0

CVSS 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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check n8n version
    Run 'n8n --version' or check the version displayed in the n8n UI (typically at the bottom of the sidebar). Compare against affected ranges: < 1.123.64, >= 2.0.0 and < 2.29.8, or exactly 2.30.0
    Affected if Installed version falls into any of the affected ranges listed
  2. Identify GraphQL nodes in workflows
    Search workflows for nodes of type 'n8n-nodes-base.graphql' or look for nodes named 'GraphQL' in the workflow editor
    Affected if GraphQL nodes exist in any active or saved workflows
  3. Identify HTTP-based credentials configured
    Navigate to Credentials in the n8n UI and filter for credentials using Header Auth, Basic Auth, Query Auth, or OAuth1/2 authentication types. These are the credential types affected by this vulnerability.
    Affected if Any credentials use Header Auth, Basic Auth, Query Auth, or OAuth authentication types
  4. Check for Allowed HTTP Request Domains configuration
    Open each HTTP-based credential identified in step 3 and inspect the 'Allowed HTTP Request Domains' field. This field should restrict which domains the credential can be used with.
    Affected if The 'Allowed HTTP Request Domains' field contains any domain restrictions (list is not empty)
  5. Check credential sharing settings
    For each HTTP-based credential with domain restrictions, open its sharing settings and check if it is shared with any non-owner users or roles
    Affected if Credentials with 'Allowed HTTP Request Domains' configured are shared with users other than the owner

A user is affected if they run a vulnerable n8n version AND use GraphQL nodes with HTTP-based credentials that have domain restrictions AND those credentials are shared with non-owner users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.123.64 / 2.29.8 or later
Fixed in 1.123.642.29.8
Interim mitigation

Upgrade to n8n versions 1.123.64, 2.29.8, or 2.30.1 or later to patch the vulnerability. Additionally, audit credential sharing settings and restrict workflow editing permissions to trusted users until the patch is applied.

Recommended fix High confidence

Upgrade to n8n version 1.123.64 (1.x branch) or 2.29.8 / 2.30.1+ (2.x branch)

  1. Identify your current n8n version by checking the n8n instance or Docker container version
  2. For self-hosted n8n: Stop the n8n service or container
  3. Update to the appropriate fixed version: 1.123.64 or later for the 1.x branch, 2.29.8 or later for the 2.x branch (excluding 2.30.0), or 2.30.1 or later
  4. Verify the upgrade was successful by checking the new version number
  5. Restart the n8n service or container
  6. Test that workflows using GraphQL node with HTTP-based credentials function correctly
  7. For managed n8n cloud instances: Contact n8n support to ensure the patch is applied
Caveat Check n8n release notes for breaking changes between your current version and the target version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in N8n Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-65596 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-65596 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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