CVE-2026-77084

This CVE exposes a privilege amplification chain in n8n's Git node: repository-local git configuration values are executed without sanitization, allowing any workflow with repository write access to achieve arbitrary code execution at n8n's privilege level. The attack surface is wider than the CVE description suggests. While the advisory notes a 'separate file-write vulnerability elsewhere' is required, this qualifier assumes file-write access is exceptional—in workflow automation, it's not. Workflows routinely write to repositories as core functionality: committing changes, updating submodules, pushing artifacts. The prerequisite for exploitation is baseline platform behavior, not a chained vulnerability. The git config consumption itself is the vulnerability. Git config values are documented extension points—designed to run arbitrary commands. The n8n node appears to have read config values and passed them to execution paths without treating them as untrusted input. This mirrors documented patterns across SSH known_hosts poisoning, .bashrc injection via shared directories, and .git/hooks exploitation—cases where repository-local state gets treated as inert configuration rather than executable input. Audit which git config keys the node reads and remove any that flow into command execution. More broadly, treat repository contents as untrusted input across the node ecosystem—this is not an isolated flaw but an instance of a recurring pattern where automation platforms inherit git's trust assumptions without accounting for multi-project execution contexts.

Reviewed through automated stages and approved by a human before publication.