How severe is GHSA-6qc9-mqvw-jg7x?

No CVSS score has been assigned to GHSA-6qc9-mqvw-jg7x yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6qc9-mqvw-jg7x?

GHSA-6qc9-mqvw-jg7x affects the following packages: n8n (npm), n8n (npm), n8n (npm). Ecosystems affected: npm.

How do I fix GHSA-6qc9-mqvw-jg7x?

Update n8n to 1.123.67 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6qc9-mqvw-jg7x is resolved across your whole dependency graph.

How do I detect GHSA-6qc9-mqvw-jg7x 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-6qc9-mqvw-jg7x if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-6qc9-mqvw-jg7x actively exploited in the wild?

No public exploit code has been indexed for GHSA-6qc9-mqvw-jg7x 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-6qc9-mqvw-jg7x?

GHSA-6qc9-mqvw-jg7x has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 37th 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-6qc9-mqvw-jg7x?

GHSA-6qc9-mqvw-jg7x is classified as CWE-639 (CWE-639). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-6qc9-mqvw-jg7x published, and has it been updated?

GHSA-6qc9-mqvw-jg7x was published on July 22, 2026 and was last updated on August 12, 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: Credential Authorization Bypass via Expression in HTTP Request Node `genericAuthType`GHSA-6qc9-mqvw-jg7x

Fix: n8n-io/n8n@f69dfc6

GHSA-6qc9-mqvw-jg7x is a CWE-639 vulnerability in n8n. A fix is available for n8n — see the affected versions and patch details below.

Also known asCVE-2026-72774

Published

Jul 22, 2026

Updated

Aug 12, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Oct 24, 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-6qc9-mqvw-jg7x.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs37th percentile — riskier than 37% 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.

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

n8nnpm

80Kdownloads / week

Description

Impact

An authenticated member with edit access to a shared workflow could reference another user's credential in an HTTP Request node while specifying the credential type through an expression. Because the pre-execution permission check compared the unresolved expression instead of the real credential type, the ownership check was skipped and the credential was loaded at execution time, letting the member use or exfiltrate a credential they were never granted. Exploitation required knowing the target credential's identifier.

Patches

The issue has been fixed in n8n versions 1.123.67, 2.31.5, and 2.32.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 n8n instance access to fully trusted users only.
Exclude the HTTP Request node by adding n8n-nodes-base.httpRequest to the NODES_EXCLUDE environment variable, if the node is not required.
Audit credential sharing and workflow access to limit exposure of credential IDs to untrusted users.

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.67`npm install n8n@1.123.67`
📦npm	`n8n`	≥ 2.32.0&&< 2.32.1	2.32.1`npm install n8n@2.32.1`
📦npm	`n8n`	≥ 2.0.0-rc.0&&< 2.31.5	2.31.5`npm install n8n@2.31.5`

Affected Products

1 product · 3 configurations

Application

n8nn8n

≥ 2.0.0 && < 2.31.5

1 version

2.32.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.67 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6qc9-mqvw-jg7x is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

## Impact An authenticated member with edit access to a shared workflow could reference another user's credential in an HTTP Request node while specifying the credential type through an expression. Because the pre-execution permission check compared the unresolved expression instead of the real credential type, the ownership check was skipped and the credential was loaded at execution time, letting the member use or exfiltrate a credential they were never granted. Exploitation required knowing the target credential's identifier. ## Patches The issue has been fixed in n8n versions 1.123.67,

O3 Security · Impact-Aware SCA

Is GHSA-6qc9-mqvw-jg7x in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works