N8N · GHSA-crfj-5wv6-8v86 · AI agents & MCP
FIX → >= 1.123.85 +2
The SeaTable Trigger node in n8n puts the credential's API token in an Authorization header, and a failed poll saves the raw HTTP error with those headers into execution data. A user who can view executions but cannot read the credential can recover the token and use it against the connected SeaTable base.
first public Oct 14, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Teams running self-hosted or managed n8n that have workflows using the SeaTable Trigger node with poll-based triggers. Exposure needs a user who can view executions but not read the credential; instances with only fully trusted users, or without SeaTable poll workflows, are less exposed.
Not affected if managed-hosting-patched, no-seatable-trigger
Who cares n8n, seatable, self-hosted
n8n --version or the n8n entry in package.json, and compare it to the fixed versions.The SeaTable Trigger node requests a base access token with the credential's API token in an Authorization header. When that request failed during polling, the raw HTTP error, including the request headers, was saved in the error execution. A user who can view the workflow's executions, but cannot read the credential, can recover the API token and use it against the connected SeaTable base.
The issue has been fixed in n8n versions 1.123.85, 2.44.1, and 2.43.5. Users should upgrade to one of these versions or later to remediate the vulnerability.
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
Upgrade to >= 1.123.85 +2
1.123.852.43.52.44.1