How severe is GHSA-cqr2-h44g-v75v?

No CVSS score has been assigned to GHSA-cqr2-h44g-v75v yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-cqr2-h44g-v75v?

GHSA-cqr2-h44g-v75v affects the following packages: n8n (npm), n8n (npm). Ecosystems affected: npm.

How do I fix GHSA-cqr2-h44g-v75v?

Update n8n to 2.38.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cqr2-h44g-v75v is resolved across your whole dependency graph.

How do I detect GHSA-cqr2-h44g-v75v 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-cqr2-h44g-v75v if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-cqr2-h44g-v75v actively exploited in the wild?

No public exploit code has been indexed for GHSA-cqr2-h44g-v75v 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-cqr2-h44g-v75v?

GHSA-cqr2-h44g-v75v has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 38th 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-cqr2-h44g-v75v?

GHSA-cqr2-h44g-v75v is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-cqr2-h44g-v75v published, and has it been updated?

GHSA-cqr2-h44g-v75v was published on September 10, 2026 and was last updated on September 10, 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: Cross-Tenant Project-Member PII Disclosure via Missing Per-Project Scope Check on Role Assignment EndpointsGHSA-cqr2-h44g-v75v

GHSA-cqr2-h44g-v75v is a CWE-862 vulnerability in n8n. A fix is available for n8n — see the affected versions and patch details below.

Also known asCVE-2026-86085

Published

Sep 10, 2026

Updated

Sep 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 27, 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-cqr2-h44g-v75v.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs38th percentile — riskier than 38% of all scored CVEsHighest risk

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

Real-World Exposure

2 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

106Kdownloads / week

Description

Impact

The endpoints /rest/roles/:slug/assignments and /rest/roles/:slug/assignments/:projectId/members checked only that the caller could manage the role type, not that they could see the project named in the request. A user holding role-management permission could therefore name any project on the instance and read back its members' names and email addresses. The patch adds a project-access check to both routes, hiding projects the caller cannot see and returning not-found for a project it cannot list.

Patches

The issue has been fixed in n8n versions 2.38.2 and 2.37.7. 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.
Audit and revoke any custom global roles that carry the role:manageProject scope, limiting that scope to fully trusted users only.

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

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`n8n`	≥ 2.38.0&&< 2.38.2	2.38.2`npm install n8n@2.38.2`
📦npm	`n8n`	all versions	2.37.7`npm install n8n@2.37.7`

Affected Products

1 product · 2 configurations

Application

n8nn8n

≥ 2.38.0 && < 2.38.2

range

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 2.38.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cqr2-h44g-v75v is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

## Impact The endpoints `/rest/roles/:slug/assignments` and `/rest/roles/:slug/assignments/:projectId/members` checked only that the caller could manage the role type, not that they could see the project named in the request. A user holding role-management permission could therefore name any project on the instance and read back its members' names and email addresses. The patch adds a project-access check to both routes, hiding projects the caller cannot see and returning not-found for a project it cannot list. ## Patches The issue has been fixed in n8n versions 2.38.2 and 2.37.7. Users sho

O3 Security · Impact-Aware SCA

Is GHSA-cqr2-h44g-v75v in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

n8n: Cross-Tenant Project-Member PII Disclosure via Missing Per-Project Scope Check on Role Assignment EndpointsGHSA-cqr2-h44g-v75v

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-cqr2-h44g-v75v in your dependencies?