The vulnerability exists in two separate locations, one for the v1 API and one for the v1beta1 API of Tekton Pipelines. In both cases, the code that validates volumeMounts for steps in a Task fails to properly sanitize the mount path. The validation logic checks if the path starts with the restricted /tekton/ prefix, but it does so without first normalizing the path. This creates a path traversal vulnerability where a user can specify a path like /tekton/home/../results, which passes the validation because it starts with the allowed /tekton/home prefix, but is later resolved by the container runtime to /tekton/results, a restricted path. This could allow an attacker to overwrite internal Tekton state, such as task results, leading to a compromise of the pipeline's integrity. The patch for this vulnerability involves using filepath.Clean to normalize the mount path before performing the prefix check, thus preventing the path traversal.