CVE-2026-103259: n8n: session token leak via Dynamic Credentials
HIGHn8n versions before 2.39.6 (and 2.40.0 before 2.40.1) leak collaborators' session tokens through the Dynamic Credentials authorize and revoke endpoints, because an authenticated user who can register a resolver can point a fallback resolver at an attacker-controlled endpoint. Exploitation is constrained: it needs high privileges, high attack complexity and a victim who must click through the account connection flow (CVSS 7.6). Nothing suggests active exploitation. The flaw is not in CISA KEV, there is no public exploit or Nuclei template, SSVC says TRACK, and EPSS is low (0.00239) though it sits in the top 86th percentile. The concern is the blast radius of a stolen session: n8n workflows hold credentials for LLM APIs, databases and SaaS systems, so a hijacked collaborator session can give broad downstream access, and the scope-changed vector reflects that. Upgrade to 2.39.6 or 2.40.1, then review who holds resolver registration rights and rotate credentials accessible to any session that may have been exposed.
What is the risk?
Medium-to-high overall. Exploitability is limited: the attacker needs an authenticated account with resolver registration rights, the attack is complex, and a victim must take part in the account connection flow. EPSS is low (0.00239), there is no public exploit, no scanner template and no KEV listing, and SSVC is TRACK. Impact is high because the vector is scope-changed with high confidentiality, integrity and availability, and a captured session token acts as the victim's identity. Risk is greatest in multi-user or shared n8n instances where many collaborators have delegated credentials to AI agents and integrations. The weakness is CWE-863 (incorrect authorization).
How does the attack unfold?
What systems are affected?
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| n8n | npm | — | No patch |
Do you use n8n? You're affected.
How severe is it?
What is the attack surface?
What should I do?
1 step1) Upgrade n8n to 2.39.6 or later on the 2.39 line, or to 2.40.1 or later on the 2.40 line. 2) Until patched, restrict the privilege to register or modify Dynamic Credentials resolvers to a minimal set of trusted administrators, and avoid completing account connection flows for resolvers you did not configure. 3) Review resolver configurations for unexpected fallback resolver URLs pointing to external or unfamiliar hosts. 4) Invalidate active sessions and force re-authentication for collaborators on exposed instances. 5) Rotate credentials stored in n8n that were reachable by potentially compromised sessions. 6) Detection: monitor outbound requests from the n8n host to unknown endpoints during authorize and revoke calls, and audit logs for resolver changes and unusual session use from new IPs. 7) Track GHSA-rx55-8qhx-4hwx and the VulnCheck advisory for updates.
What does CISA's SSVC say?
Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.
How is it classified?
Which compliance frameworks are affected?
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2026-103259?
n8n versions before 2.39.6 (and 2.40.0 before 2.40.1) leak collaborators' session tokens through the Dynamic Credentials authorize and revoke endpoints, because an authenticated user who can register a resolver can point a fallback resolver at an attacker-controlled endpoint. Exploitation is constrained: it needs high privileges, high attack complexity and a victim who must click through the account connection flow (CVSS 7.6). Nothing suggests active exploitation. The flaw is not in CISA KEV, there is no public exploit or Nuclei template, SSVC says TRACK, and EPSS is low (0.00239) though it sits in the top 86th percentile. The concern is the blast radius of a stolen session: n8n workflows hold credentials for LLM APIs, databases and SaaS systems, so a hijacked collaborator session can give broad downstream access, and the scope-changed vector reflects that. Upgrade to 2.39.6 or 2.40.1, then review who holds resolver registration rights and rotate credentials accessible to any session that may have been exposed.
Is CVE-2026-103259 actively exploited?
No confirmed active exploitation of CVE-2026-103259 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-103259?
1) Upgrade n8n to 2.39.6 or later on the 2.39 line, or to 2.40.1 or later on the 2.40 line. 2) Until patched, restrict the privilege to register or modify Dynamic Credentials resolvers to a minimal set of trusted administrators, and avoid completing account connection flows for resolvers you did not configure. 3) Review resolver configurations for unexpected fallback resolver URLs pointing to external or unfamiliar hosts. 4) Invalidate active sessions and force re-authentication for collaborators on exposed instances. 5) Rotate credentials stored in n8n that were reachable by potentially compromised sessions. 6) Detection: monitor outbound requests from the n8n host to unknown endpoints during authorize and revoke calls, and audit logs for resolver changes and unusual session use from new IPs. 7) Track GHSA-rx55-8qhx-4hwx and the VulnCheck advisory for updates.
What systems are affected by CVE-2026-103259?
This vulnerability affects the following AI/ML architecture patterns: agent frameworks, workflow automation platforms, LLM orchestration pipelines, multi-tenant collaborative AI platforms.
What is the CVSS score for CVE-2026-103259?
CVE-2026-103259 has a CVSS v3.1 base score of 7.6 (HIGH). The EPSS exploitation probability is 0.24%.
What is the AI security impact?
Affected AI Architectures
MITRE ATLAS Techniques
AML.T0012Valid AccountsAML.T0083Credentials from AI Agent ConfigurationAML.T0091.000Application Access TokenCompliance Controls Affected
What are the technical details?
Original Advisory
n8n versions before 2.39.6 and 2.40.0 before 2.40.1 contain a session token leakage vulnerability in the Dynamic Credentials authorize and revoke endpoints. Attackers with resolver registration capability can capture collaborators' session tokens by setting a fallback resolver to an attacker-controlled endpoint during the account connection flow, enabling unauthorized credential access.
Exploitation Scenario
A malicious or compromised insider with resolver registration rights on a shared n8n instance sets the fallback resolver of a Dynamic Credentials configuration to an endpoint they control. They then invite or socially nudge a colleague who manages AI agent workflows to connect an account through the normal flow. When the victim's authorize or revoke request is processed, their session token is sent to the attacker's endpoint. The attacker replays the token to impersonate the colleague, reads workflows and stored credentials for LLM providers and databases, and modifies an agent workflow to exfiltrate data or abuse connected tools.
Weaknesses (CWE)
CWE-863 — Incorrect Authorization: The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
- [Architecture and Design] Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
- [Architecture and Design] Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor [REF-7].
Source: MITRE CWE corpus.
CVSS Vector
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:HReferences
Timeline
Related Vulnerabilities
CVE-2026-3366310.0n8n: member role steals plaintext HTTP credentials
Same package: n8nCVE-2026-3366010.0TensorFlow: type confusion NPD in tensor conversion
Same package: n8nCVE-2026-2185810.0n8n: Input Validation flaw enables exploitation
Same package: n8nCVE-2026-275779.9n8n: Code Injection enables RCE
Same package: n8nCVE-2026-274949.9n8n: security flaw enables exploitation
Same package: n8n