---
id: "CVE-2026-126385"
page: "https://infrastack.ai/live/CVE-2026-126385"
kind: "vulnerability"
aliases: ["CVE-2026-126385"]
title: "n8n: OAuth2 callback lets a member store a victim's tokens"
severity: "high"
cvss: 7.7
epss: null
exploited: false
status: "open"
category: "ai-tooling"
products: []
ecosystems: []
tags: ["ai-tooling", "n8n", "oauth2", "self-hosted", "workflow-automation"]
not_affected_if: ["managed-hosting-patched", "no-oauth2-credentials", "single-user-instance"]
published_at: "2026-11-13T10:17:41+00:00"
first_seen_at: "2026-11-13T10:47:18+00:00"
updated_at: "2026-11-13T10:52:32+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-126385", "first_seen_at": "2026-11-13T10:47:18+00:00"}]
exploit_sources: []
---

# n8n: OAuth2 callback lets a member store a victim's tokens

Link for people: https://infrastack.ai/live/CVE-2026-126385 (this .md is for agents)

n8n's OAuth2 credential callback in the dynamic-credential connect flow does not check that the browser completing the flow belongs to the user who started it. A member with access to an OAuth2 credential can send the provider's authorization link to a victim, and if the victim consents without an active n8n session, the victim's tokens are stored under the member's account so the member's workflows act as the victim.

_Summary, check and fix written by a model from the sources; labelled as such._

## Fix

- n8n `2.45.5` or later on the 2.45 line
- n8n `2.46.1` or later on the 2.46 line
- n8n `3.0.1` or later on the 3.x line

## Timeline

- 2026-11-13T10:47:18+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-126385

## Documents

- [advisory] Maintainer's advisory: github.com https://github.com/n8n-io/n8n/security/advisories/GHSA-426f-xmcv-g8pg
- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/n8n-before-2.46.1-oauth-account-hijack-via-unauthenticated-credential-callback

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_