How severe is GHSA-q3j5-8vrg-4p9q?

No CVSS score has been assigned to GHSA-q3j5-8vrg-4p9q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-q3j5-8vrg-4p9q?

GHSA-q3j5-8vrg-4p9q affects the following packages: n8n (npm), n8n (npm), n8n (npm). Ecosystems affected: npm.

How do I fix GHSA-q3j5-8vrg-4p9q?

Update n8n to 1.123.61 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q3j5-8vrg-4p9q is resolved across your whole dependency graph.

How do I detect GHSA-q3j5-8vrg-4p9q in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for n8n, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-q3j5-8vrg-4p9q if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-q3j5-8vrg-4p9q actively exploited in the wild?

No public exploit code has been indexed for GHSA-q3j5-8vrg-4p9q yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-q3j5-8vrg-4p9q?

GHSA-q3j5-8vrg-4p9q has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 32th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-q3j5-8vrg-4p9q?

GHSA-q3j5-8vrg-4p9q is classified as Information Exposure (CWE-200), CWE-522 (CWE-522). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-q3j5-8vrg-4p9q published, and has it been updated?

GHSA-q3j5-8vrg-4p9q was published on July 22, 2026 and was last updated on July 22, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

n8n: Shared Credential Header Leak via HTTP Request Pagination ExpressionGHSA-q3j5-8vrg-4p9q

GHSA-q3j5-8vrg-4p9q is a Information Exposure vulnerability in n8n. A fix is available for n8n — see the affected versions and patch details below.

Also known asCVE-2026-59209

Published

Jul 22, 2026

Updated

Jul 22, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Oct 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-q3j5-8vrg-4p9q.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs32th percentile — riskier than 32% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

37other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

n8nnpm

110Kdownloads / week

Description

Impact

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. When an HTTP Header Auth credential is applied to a paginated request, the secret is present in $request.headers when pagination expressions are evaluated. A user-controlled expression could read that secret, copy it into item data, and exfiltrate it through a later HTTP Request node, bypassing credential domain restrictions, since the secret leaves via item data rather than the credential's own request mechanism.

This issue only affects instances with N8N_EXPRESSION_ENGINE=vm set, where paginated HTTP Request workflows using shared credentials are accessible to non-owner users.

Patches

The issue has been fixed in n8n versions 1.123.61, 2.27.4, and 2.28.1. Users should upgrade to one of these versions or later to remediate the vulnerability.

Workarounds

If upgrading is not immediately possible, administrators should consider the following temporary mitigations:

Restrict workflow sharing to fully trusted users only.
Avoid sharing credentials with use-only access to untrusted users on workflows that use HTTP Request nodes with pagination enabled.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`n8n`	all versions	1.123.61`npm install n8n@1.123.61`
📦npm	`n8n`	≥ 2.28.0&&< 2.28.1	2.28.1`npm install n8n@2.28.1`
📦npm	`n8n`	≥ 2.0.0-rc.0&&< 2.27.4	2.27.4`npm install n8n@2.27.4`

Affected Products

1 product · 6 configurations

Application

n8nn8n

≥ 2.0.0 && < 2.27.4

1 version

2.28.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for n8n, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update n8n to 1.123.61 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q3j5-8vrg-4p9q is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

## Impact 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. When an HTTP Header Auth credential is applied to a paginated request, the secret is present in `$request.headers` when pagination expressions are evaluated. A user-controlled expression could read that secret, copy it into item data, and exfiltrate it through a later HTTP Request node, bypassing credential domain restrictions, since the secret leaves via item data rather than the creden

O3 Security · Impact-Aware SCA

Is GHSA-q3j5-8vrg-4p9q in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

n8n: Shared Credential Header Leak via HTTP Request Pagination ExpressionGHSA-q3j5-8vrg-4p9q

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

Real-World Exposure

Description

Impact

Patches

Workarounds

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-q3j5-8vrg-4p9q in your dependencies?