Skip to main content
VulnerabilityPublished

CVE-2026-103259: n8n · Incorrect Authorization

Affects n8nSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.5 High : upgrade to 2.40.1 or 2.39.6 soon.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 4.0 base score
8.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.40.1, 2.39.6
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:A/VC:H/VI:H/VA:H/SC:H/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade n8n and n8n-io/n8n to 2.40.1 or 2.39.6.

Affected software

ProductAffectedFixed in
n8n-ion8nAffected
  • >=2.40.0 <2.40.1
Fixed in
  • 2.40.1
n8n-ion8nAffected
  • <2.39.6
Fixed in
  • 2.39.6
GitHubn8n-io/n8npkg:github/n8n-io/n8nOther threatsAffected
  • <2.39.6
  • >=2.40.0 <2.40.1
Fixed in
  • 2.39.6
  • 2.40.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in n8n versions 2.39.6 and 2.40.1. Users should upgrade to these or later versions to remediate the vulnerability. No additional mitigation steps are indicated by the vendor advisory.

Description

n8n versions before 2.39.6 and versions from 2.40.0 up to but not including 2.40.1 have a session token leakage vulnerability in the Dynamic Credentials authorize and revoke endpoints. Attackers with resolver registration capability can exploit this by setting a fallback resolver to an attacker-controlled endpoint during the account connection flow, allowing them to capture collaborators' session tokens and gain unauthorized access to credentials.

References

Community reviews

Loading reviews…