Kubescape Repo Shows Artifact Poisoning Risk (INJ-002), Downgraded to Low Severity

A potential artifact poisoning vulnerability (INJ-002) has been flagged in the popular Kubernetes security tool repository, slashben/kubescape. The finding, initially assessed as a medium-severity risk, was downgraded to low after automated verification failed to successfully exploit the configuration weakness. This highlights the gap between theoretical security misconfigurations and their practical exploitability in CI/CD pipelines.

The specific issue centers on two GitHub Actions workflows that use `fetch-depth: 0` without the corresponding `persist-credentials: false` setting. This combination creates a `.git/` directory containing the GITHUB_TOKEN credentials, a classic precondition for the 'artipacked' attack vector. However, the critical exploit chain was broken: neither workflow contains any `actions/upload-artifact` steps or other mechanisms that would expose these credentials. The artipacked vulnerability requires such artifact uploads to be practically exploitable, turning this into a configuration oversight rather than an active vulnerability.

The case underscores a key dynamic in supply chain security: not all flagged misconfigurations lead to immediate compromise. For projects like Kubescape, which are central to the cloud-native security ecosystem, even low-severity findings prompt scrutiny of development practices. The adjustment from medium to low severity reflects a verification-driven approach, where automated agents test hypotheses before final judgment. It serves as a reminder for maintainers to audit CI/CD workflows for unnecessary credential persistence, even when the direct path to exploitation is currently blocked.