cve.bz

CVE-2026-126385 n8n before 2.46.1 OAuth Account Hijack via Unauthenticated Credential Callback

4.8 mediumEPSS 0.3%

Medium (4.8) in n8n-io n8n. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
n8n before 2.45.5, 2.46.x before 2.46.1, and 3.x before 3.0.1 contains a flaw in the OAuth2 credential callback of the dynamic-credential connect flow, which does not verify that the completing browser belongs to the user who started the flow. Members with access to a resolvable OAuth2 credential can send the provider authorization URL to a victim; if the victim consents without an active n8n session, the victim's tokens are stored under the member's identity, letting the member's workflows act as the victim.

Severity

CVSS 4.0

4.8 medium
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N

CVSS 3.1

7.7 high
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 26th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-306 Missing Authentication for Critical Functionality
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
Assigned by
VulnCheck (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-126385 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126385?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126385?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-126385 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-126385

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-126385](https://cve.bz/cve/badge/CVE-2026-126385.svg)](https://cve.bz/cve/CVE-2026-126385)

HTML:

<a href="https://cve.bz/cve/CVE-2026-126385"><img src="https://cve.bz/cve/badge/CVE-2026-126385.svg" alt="CVE-2026-126385"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
n8n-io n8nfrom 2.46.0 before 2.46.1
n8n-io n8nbefore 2.45.5
n8n-io n8nfrom 3.0.0 before 3.0.1

Attack patterns (CAPEC)

  • CAPEC-12 Choosing Message Identifier Likelihood: High · Severity: High
  • CAPEC-36 Using Unpublished Interfaces or Functionality Likelihood: Medium · Severity: High
  • CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
  • CAPEC-166 Force the System to Reset Values Severity: Medium
  • CAPEC-216 Communication Channel Manipulation

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON