Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLog in as execution-read user
-
DeliveryLocate SeaTable trigger error execution
-
ExploitRead raw request headers in error data
-
ExecutionExtract API token from Authorization header
-
ImpactAccess connected SeaTable base
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A09:2025 - Security Logging & Alerting Failures
ASVS 5.0
V16 - Security Logging and Error Handling Log data sanitization
|
| Exploitation Conditions | Requires an authenticated n8n user who holds execution-read permission but is denied credential-read permission (the exact trust boundary the flaw crosses). The instance must run a SeaTable Trigger node in poll mode, and a poll request to obtain the base access token must have actually failed - only then is the raw HTTP error, including the Authorization header with the API token, written into the error execution record. Limiting factors: exploitation is impossible without a prior poll failure having been recorded, requires existing low-privilege access to the n8n instance (PR:L, not remote-unauthenticated), and only affects deployments actually using SeaTable poll triggers on vulnerable versions (n8n < 1.123.85, 2.x < 2.43.5, 2.44.x < 2.44.1). |
| Impact | This is a moderate-severity information-disclosure flaw (CWE-532), and the signals are internally consistent rather than conflicting. The CVSS 4.0 vector (AV:N/AC:L/AT:P/PR:L/UI:N) indicates a network-reachable issue but one that requires an already-authenticated low-privilege user (PR:L) and a specific precondition (AT:P) - namely that a SeaTable poll request actually failed and wrote raw headers into error execution data. This is not a remote-unauthenticated break-in; it is a privilege/trust-boundary bypass where a user who can read executions but is denied credential access recovers a secret they should not see. The vuln.today decision label is 'this_month' (not act_now/emergency), which matches the absence of CISA KEV listing and the lack of any provided EPSS score or PoC/exploit reference. No active exploitation is claimed and no public exploit is referenced in the input. The direct technical impact is limited (token disclosure, VC:L), but the 4.0 subsequent-system metrics (SC:H/SI:H) correctly capture that the leaked token grants confidentiality and integrity access to the connected SeaTable base - a real lateral-impact concern. Net: a legitimate patch-this-cycle issue for n8n operators who run SeaTable poll triggers and have users with execution-read-but-not-credential-read roles, but not an internet-facing emergency. Note that EPSS and KEV data are absent from the input, so widespread-exploitation probability could not be quantified. |
| Exploit ScenarioDerived | An n8n operator grants a team member read access to workflow executions but withholds access to stored credentials. A SeaTable Trigger node running in poll mode experiences a failed base-token request, and n8n saves the raw HTTP error - including the Authorization header carrying the API token - into the error execution record. The low-privilege user opens that execution, reads the token out of the stored request headers, and uses it to access and modify the connected SeaTable base. No public exploit code is referenced in the input; exploitation is trivial manual inspection requiring only existing execution-read access. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 28, 2026
n8n before 1.123.85, 2.x before 2.43.5, and 2.44.x before 2.44.1 leak the SeaTable Trigger node's API token into error execution data, because failed poll requests persist raw request headers - including the Authorization header carrying the credential's API token. An authenticated n8n user who can view a workflow's executions but is denied permission to read its credentials can recover that token and use it directly against the connected SeaTable base. Exploitation requires a prior poll failure to have been recorded and a SeaTable poll trigger to be in use, so only deployments matching those conditions are exposed; no public exploit code has been identified at time of analysis and the CVE is not in CISA KEV, with the vendor advisory published as GHSA-crfj-5wv6-8v86.
RemediationAI
Vendor-released patch: upgrade n8n to 1.123.85, 2.43.5, or 2.44.1 (or later) depending on the branch in use - the advisory fixes the issue in all three. Per the vendor advisory, if upgrading is not immediately possible, administrators can 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, and restrict execution read access to the minimum set of users who require it. The vendor explicitly states these workarounds do not fully remediate the risk and are appropriate only as short-term measures; the complete fix is the upgrade. Because only a prior failed poll request leaves the token in execution data, rotating tokens used by SeaTable poll triggers also invalidates any token already captured.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is CWE-532 (Insertion of Sensitive Information into Log File), applied here to n8n's execution-record persistence rather than to a traditional text log. n8n is a workflow automation platform distributed as the npm package n8n; the SeaTable Trigger node runs in poll mode and periodically requests a base access token, sending the configured credential's API token in an HTTP Authorization header. When that token request fails, the raw HTTP error is written into the error execution record together with the request headers, so the API token ends up stored inside an object that is governed by execution-read permissions rather than credential-read permissions. The result is a permission-boundary defect: an actor holding execution-read but not credential-read rights can read the stored header and lift a secret the UI intentionally hides. The trigger mechanism beyond the failed poll request is not described in the available sources; the advisory does not characterise whether the failure is any HTTP error or a narrower subset. Affected package ranges are npm/n8n < 1.123.85, < 2.43.5 on the 2.x line, and < 2.44.1 on the 2.44.x line. The assessed vector CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N (with the secondary scope change) reflects that the impact is confined to confidentiality of the SeaTable token and the connected base, with high attack complexity because a recorded poll failure is a precondition.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:H/SI:H/SA:N
Network-reachable but needs a low-privilege execution-reader (PR:L) and a prior poll failure to store the token (AC:H); scope change (S:C) captures access to the separate SeaTable base, with token disclosure as C:L.
Primary rating from Vendor (vulncheck).
CVSS VectorVendor: vulncheck
Lifecycle Timeline
1DescriptionCVE.org
n8n before 1.123.85, 2.x before 2.43.5, and 2.44.x before 2.44.1 saves the SeaTable Trigger node's API token in error execution data, because failed poll requests store raw request headers. Users who can view workflow executions but cannot read the credential can recover the token and access the connected SeaTable base.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-112378
GHSA-gw76-wmfv-8jqv
NVD
CVE.org
Exploit-DB