Advisory

GHSA-pq6c-vh67-xpm3

Also known as: CVE-2026-86993

Summary

n8n: Log Streaming Event Destinations Decrypt Generic-Auth Credentials Without Ownership Check

Details

Impact

A log streaming event destination may reference a generic HTTP credential, and the destination resolved and decrypted whichever credential it named without checking that the caller had access to it. A user holding a custom global role scoped to Log Streaming operations could therefore name a credential belonging to another project and have its decrypted secret sent to an endpoint they controlled. The patch applies the standard credential access check when a destination resolves its credential.

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.
  • Audit and revoke any custom global roles that carry Log Streaming scopes (eventBusDestination:create, eventBusDestination:test, etc.), limiting those scopes to fully trusted users only.
  • Review existing Log Streaming event destinations for unexpected webhook URLs and remove any that are not recognized, then rotate any credentials that may have been referenced.

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

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-09-10 21:07 UTC
Modified
2026-09-10 21:15 UTC

Affected packages and fixes

n8n

npm · All systems

Affected

  • introduced 0, fixed 1.123.76 (semver)

Fixed versions

1.123.76

Fix

n8n

npm · All systems

Affected

  • introduced 2.38.0, fixed 2.38.2 (semver)

Fixed versions

2.38.2

Fix

n8n

npm · All systems

Affected

  • introduced 2.0.0, fixed 2.37.7 (semver)

Fixed versions

2.37.7

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences