SeaTable Trigger Node Stores the API Token in Failed Poll Execution Data
Summary
Impact
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, b...
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| npm | n8n |
< 1.123.85 |
>= 1.123.85 |
| npm | n8n |
< 2.44.1 |
>= 2.44.1 |
| npm | n8n |
< 2.43.5 |
>= 2.43.5 |
Original description The description as published by the source.
Impact
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.
Patches
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.
Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Restrict n8n instance access to fully trusted users only.
- Deactivate SeaTable poll-trigger workflows until the instance is patched.
- Rotate any SeaTable API tokens used by poll-trigger workflows and audit recent execution records for unexpected token exposure.
- Restrict execution read access to the minimum set of users who require it.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Source: GitHub Repository Security Advisories (Game のスタック) GitHub Advisory OSV
References
- GITHUB_REPO_ADVISORY n8n-io/n8n