Technical impact
The flaw allows CI automation scripts to store GitHub access tokens in plaintext on runners without purging them after job completion. Because the tokens are not protected, an attacker who can access the CI environment can read these exposed credentials. With the credentials, the attacker could obtain unauthorized access to the associated GitHub repositories, enabling modification of source code, deployment of malicious artifacts, or other destructive actions. The weakness is a lack of secure handling of secrets, as categorized by CWE‑312.
Affected Systems
konflux‑ci – the CI/CD platform that orchestrates automated build and deployment pipelines. The vulnerability is observed in the default configuration where scripts write tokens to disk during processing. No specific product version range is disclosed in the advisory, so any instance running the vulnerable konflux‑ci code is potentially affected.
Risk and Exploitability
The CVSS score of 8.6 marks this issue as high severity, indicating significant impact if exploited. EPSS score: not available, and the vulnerability is not listed in the CISA KEV catalog, but the lack of these metrics does not preclude exploitation. The likely attack vector requires local access to the CI environment, such as a user with write permissions to the runner or a compromise of the host system, implying that securing the runner infrastructure and restricting local privilege are critical. Once the attacker extracts the stored token, they can authenticate to GitHub and perform any action authorized for that token, leading to potential data corruption or release tampering.