The `parseEnv` function omits `VISUAL` from `GitEnvKeys`, causing `prepareEnv` to drop the value before `vulnerabilityCheck()` can classify it as `allowUnsafeEditor`. In applications that forward attacker-influenced environment values, this allows Git to invoke an attacker-selected editor during operations like commit amendment or interactive rebase, provided no higher-priority editor setting overrides `VISUAL` and terminal prerequisites are met. The executed editor runs with the privileges of the Node.js process.