The vulnerability stems from missing Run/Artifacts permission checks in artifact access logic, but the provided data lacks specific code references, commit diffs, or file paths. While the advisory describes the flawed authorization mechanism, it does not explicitly name the functions responsible for artifact retrieval or permission validation. Without concrete code examples or patch details, identifying exact vulnerable functions with high confidence is not possible. The fix likely involved adding permission checks in artifact-serving endpoints or controllers, but these cannot be mapped to specific functions without further technical context.