CVE-2026-86994
mediumpriority · track · 17OT risk · elevatedEPSS 0.003 · 28 %ileDEUSEPSS · scored 2026-10-27
n8n is an open source workflow automation platform. Prior to 1.123.76, 2.37.7, and 2.38.2, the /rest/active-workflows endpoint returned every active workflow ID on the instance to any member regardless of sharing. Workflow activation, deactivation, and publication push events were also broadcast to clients that could not access the affected workflow, disclosing workflow IDs, version IDs, and activation error details. The affected paths include packages/cli/src/services/active-workflows.service.ts and packages/cli/src/workflows/workflow-push-notifier.service.ts. This issue is fixed in versions 1.123.76, 2.37.7 and 2.38.2.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · low–medium · 1.3–5.3
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (12)
Products and version ranges known to be affected.
advisories (2)
Vendor and ecosystem advisories describing this.
- WID-SEC-W-2026-3165n8n: Mehrere SchwachstellenDeutsch2026-09-02csaf · cert_bundDE
Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in n8n ausnutzen, um Sicherheitsmechanismen zu umgehen, beliebigen Code auszuführen oder einen Denial of Service zu verursachen.
- GHSA-65xw-2v52-jhxcn8n: Cross-User Active Workflow ID and Lifecycle Event Disclosure via Missing userId Filter2026-09-10ghsa · osvUS
## Impact The endpoint `/rest/active-workflows` returned every active workflow ID on the instance to any member, regardless of sharing, and workflow activation, deactivation and publication push events were broadcast to every connected client, carrying workflow IDs, version IDs and activation-error detail across users. The patch scopes both the listing and the push events through the sharing service, so a user only sees workflows they can access. ## Patches The issue has been fixed in n8n versions 1.123.76, 2.37.7, and 2.38.2. 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. - Avoid provisioning `global:member` accounts for untrusted users until the instance is patched. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
sources
Which sources assert this record, and when.
references (4) nvd
External citations — patches, advisories, analysis.
- https://github.com/n8n-io/n8n/releases/tag/n8n@1.123.76Release Notes
- https://github.com/n8n-io/n8n/releases/tag/n8n@2.37.7Release Notes
- https://github.com/n8n-io/n8n/releases/tag/n8n@2.38.2Release Notes
- https://github.com/n8n-io/n8n/security/advisories/GHSA-65xw-2v52-jhxcMitigationVendor Advisory
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan