For your digest
n8n-mcp: n8n-mcp's IPv4-mapped IPv6 addresses bypass SSRF protection in validateUrlSync(), enabling full SSRF for SDK embedders
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
n8n-mcp (npm)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- n8n-mcp (npm): from 2.47.4, before 2.47.14
The fix
n8n-mcp (npm) fixed in 2.47.14
npmnpm install n8n-mcp@2.47.14pnpmpnpm add n8n-mcp@2.47.14yarnyarn add n8n-mcp@2.47.14bunbun add n8n-mcp@2.47.14Check what is installednpm ls n8n-mcpPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency n8n-mcp to 2.47.14 or the nearest later release, to fix CVE-2026-42449. 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
No evidence that it is being used, or can be. It is listed because of what it affects.
Timeline
- First published here, as "For your digest".