The vulnerability stems from two primary issues:

1. The ExecCommandError's Error() and DetailedError() methods in ops.go logged command arguments and environment variables containing the PullSecretToken without sanitization. The patch introduced a 'removePullSecret' function to redact this sensitive data, confirming these functions were leaking secrets.
2. The ops.ExtractFromIgnition function had a log message explicitly mentioning 'pull secret', which was modified to a generic 'data' reference. While this change reduces information disclosure, the higher-confidence leak occurred in command execution logging. The ControllerConfig struct modification (adding 'secret:"true"') suggests framework-level protections, but the direct logging in command execution paths was the root cause.