CVE-2026-86073 n8n-io CVE debrief

Who should care

Defenders managing n8n workflows and OAuth token configurations should assess exposure and prioritize verification and remediation. This includes reviewing and updating workflow configurations to prevent unauthorized access, verifying and upgrading to n8n versions 2.37.7 or 2.38.1 if using earlier versions, and assessing exposure for workflows using OAuth tokens. Additionally, defenders should review compensating controls for exposed systems while remedi

Why it matters

CVE-2026-86073 allows unauthorized access to n8n workflows via OAuth token endpoint manipulation, impacting defenders managing workflow configurations and OAuth tokens.

• Unauthorized access to unapproved workflows
• Potential for lateral movement within n8n workflows
• Need for verification of workflow configurations and OAuth token settings
• Priority for upgrading to patched n8n versions

Technical summary

The n8n OAuth token endpoint vulnerability allows an OAuth client approved for one workflow to substitute a different workflow URL and obtain a valid token for an unapproved workflow accessible to the consenting user. This issue is fixed in versions 2.37.7 and 2.38.1. The vulnerability impacts defenders managing workflow configurations and OAuth tokens, allowing unauthorized access to unapproved workflows and potential for lateral movement within n8n workflows. Defenders should prioritize verifying and upgrading to n8n versions 2.37.7 or 2.38.1 if using earlier versions, and assess exposure for workflows using OAuth tokens.

Defensive priority

Defenders should prioritize verifying and upgrading to n8n versions 2.37.7 or 2.38.1 if using earlier versions, and assess exposure for workflows using OAuth tokens.

Recommended defensive actions

• Verify and upgrade to n8n versions 2.37.7 or 2.38.1 if using earlier versions.
• Assess exposure for workflows using OAuth tokens and ensure proper authorization.
• Review and update workflow configurations to prevent unauthorized access.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The CVE record and NVD entry provide details on the OAuth token endpoint vulnerability in n8n, which allows an OAuth client approved for one workflow to substitute a different workflow URL and obtain a valid token for an unapproved workflow.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.