n8n-io · n8n · published 2026-09-08
CVE-2026-86993n8n: Log Streaming Event Destinations Decrypt Generic-Auth Credentials Without Ownership Check
Routine No exploitation evidence; EPSS 0.5%.
CVE-2026-86993 is not known to be exploited in the wild. EPSS estimates a 0.5% chance of exploitation in the next 30 days, higher than 40% of all CVEs. This n8n vulnerability: CVSS 5.9 (v4.0). Fixed upstream in n8n 2.38.2, 2.37.7, 1.123.89, 1.123.76. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in n8n 2.38.2, 2.37.7, 1.123.89, 1.123.76.
Patch events
AI toolingn8n
n8n security releases: 2.38.2, 2.37.7, 1.123.89, 1.123.76
Upgrade to
2.38.22.37.71.123.891.123.76Why: Vendor security release for server software (most severe: CVE-2026-86075).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.5% (41th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 5.9 (v4.0)CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- n8n-io n8n
>= 2.38.0, < 2.38.2(affected)>= 2.0.0, < 2.37.7(affected)< 1.123.76(affected)
Description (from the CVE record)#
n8n is an open source workflow automation platform. Prior to 1.123.76, 2.37.7, and 2.38.2, a Log Streaming event destination could reference a generic HTTP credential and decrypt whichever credential ID it named without an ownership check. A user with a custom global role carrying Log Streaming scopes could select a credential belonging to another project and send its decrypted secret to an attacker-controlled endpoint. The affected authorization boundary is packages/cli/src/modules/log-streaming.ee/destinations/destination-credentials-access.ts and the credential:read scope. This issue is fixed in versions 1.123.76, 2.37.7 and 2.38.2.
Quoted from the CVE Program record.