The vulnerability stems from two key issues: 1) The Job definition was constructed using a YAML template (job.template.yaml) that directly incorporated unvalidated user inputs from MustGather CR specs, allowing template injection (CWE-1336). 2) The service account selection and command construction mechanisms (visible in PR #135 and #138 changes) allowed users to specify privileged contexts. The processJobTemplate function was particularly vulnerable as it directly processed user inputs into the Job template, while getClusterVersionForJobTemplate's version handling could enable further exploitation vectors. The fixes in PR #135 and #138 that removed template-based construction and implemented strict struct-based validation confirm these functions' roles in the vulnerability chain.