I think you missed my question :) I understand the security concerns (arbitrary code execution just by loading an arbitrary file into vim). My question was: t

I think you missed my question :) I understand the security concerns (arbitrary code execution just by loading an arbitrary file into vim). My question was: this issue was caught, diagnosed, widely publicised and the configuration fix for it was widely deployed - nearly 15 (fifteen!) years ago. So why is it cropping up as a "new" security issue now?