N8n-io n8n
n8n before 2.46.1 OAuth Account Hijack via Unauthenticated Credential Callback
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 2.46.0, < 2.46.1
Fixed in 2.46.1
- < 2.45.5
Fixed in 2.45.5
- >= 3.0.0, < 3.0.1
Fixed in 3.0.1
Mitigation
Upgrade n8n to 2.46.1 or later.
Upgrade n8n to 2.45.5 or later.
Upgrade n8n to 3.0.1 or later.
References
- Vendor advisory github.com/n8n-io/n8n/security/advisories/GHSA…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.