Advisories
This weekExploitable · Confirmed

n8n: n8n Privilege Escalation vulnerability

There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.

Does it affect what I run?

n8n (npm)

Checked in your browser. The version you type is not sent anywhere.

Who is affected

  • n8n (npm): every version, before 0.216.1

The fix

  • n8n (npm) fixed in 0.216.1

    npm
    npm install n8n@0.216.1
    pnpm
    pnpm add n8n@0.216.1
    yarn
    yarn add n8n@0.216.1
    bun
    bun add n8n@0.216.1
    Check what is installed
    npm ls n8n
    Paste into Cursor, Lovable or Claude Code
    Upgrade the npm dependency n8n to 0.216.1 or the nearest later release, to fix CVE-2023-27563. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.

Fix commands generated from the advisory's versions. No model wrote them.

In plain words

Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.

Evidence

Timeline

  1. First published here, as "For your digest".
  2. Level changed from "For your digest" to "This week".
  3. Evidence added: CISA's assessment in the CVE record says a proof of concept is public. (CISA Vulnrichment (SSVC and KEV fields inside CVE records))