dbcve.org
N8nApplication

CVE-2026-59209

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-09
Fix available
A fix is available. Upgrade to 1.123.61 / 2.27.4 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 6 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 is an open source workflow automation platform. Prior to 1.123.61, 2.27.4, and, 2.28.1, an authenticated member with use-only editor access to a shared workflow could read credential-populated headers exposed via the $request object inside an HTTP Request node's pagination expression and exfiltrate the secret through item data. This issue is fixed in versions 1.123.61, 2.27.4, and 2.28.1.

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 confidence

An authenticated user with use-only editor access to a shared workflow could read credential-populated headers via the $request object in an HTTP Request node's pagination expression, allowing exfiltration of secrets through item data.

MitigationUpgrade to n8n versions 1.123.61, 2.27.4, or 2.28.1 or later. Audit workflows using HTTP Request nodes with pagination that contain credentials to identify potential credential exposure.

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.61>= 2.0.0, < 2.27.4= 2.28.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
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 checks

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

  1. Check n8n version
    Run 'n8n --version' or check the version in the UI footer. For Docker, check the image tag. For self-hosted, check package.json or the /rest/version API endpoint.
    Affected if The installed version is < 1.123.61, or >= 2.0.0 and < 2.27.4, or exactly 2.28.0.
  2. Identify workflows with HTTP Request nodes
    Search workflow JSON exports or use the API at /rest/workflows to list all workflows, then inspect each for nodes of type 'n8n-nodes-base.httpRequest' that have pagination enabled (property 'pagination.enabled' = true).
    Affected if Any workflow contains an HTTP Request node with pagination turned on.
  3. Check for credentials in HTTP Request nodes with pagination
    In workflows identified in step 2, examine the node parameters for 'authentication' or 'header' fields that reference credential objects (typically IDs starting with 'credential_'). Focus on headers that may contain secrets.
    Affected if The HTTP Request node with pagination references credentials in authentication or header parameters.
  4. Review workflow sharing permissions
    Check the 'shared' array in workflow settings via the API or UI. Identify if any users or roles have only 'use' or 'editor' access (not 'admin' or 'owner') to workflows identified in step 3.
    Affected if The workflow with HTTP Request nodes containing credentials and pagination is shared with users who have only 'use' or 'editor' role permissions.

You are affected if your n8n version is vulnerable AND you have workflows with HTTP Request nodes using pagination that reference credentials and 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.61 / 2.27.4 or later
Fixed in 1.123.612.27.4
Interim mitigation

Upgrade to n8n versions 1.123.61, 2.27.4, or 2.28.1 or later. Audit workflows using HTTP Request nodes with pagination that contain credentials to identify potential credential exposure.

Recommended fix High confidence

1.123.61 (for 1.x users) OR 2.27.4 (for 2.0.0-2.27.x users) OR 2.28.1 (for 2.28.0 users)

  1. 1. Identify your current n8n version by checking the running instance or your deployment configuration
  2. 2. Determine which version branch you are on (1.x or 2.x)
  3. 3. If on 1.x branch (< 1.123.61): Upgrade to version 1.123.61 or later
  4. 4. If on 2.x branch (>= 2.0.0, < 2.27.4): Upgrade to version 2.27.4 or later
  5. 5. If on 2.28.0: Upgrade to version 2.28.1 or later
  6. 6. After upgrading, verify the n8n instance is running correctly
  7. 7. Test that workflows with HTTP Request nodes and pagination expressions work as expected

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

Fix this in N8n Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-59209 — 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-59209 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