Konflux-ci: github token plaintext exposure in ci/cd scripts
Affects konflux-ci v0.2.2, v0.2.3-rc.0, and the main branch, whose CI scripts store the GitHub token in ~/.git-credentials. No vendor rating or fixed version is listed.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Konflux-ci continuous integration automation scripts are affected, as they leave GitHub access tokens stored in plaintext on the CI runner after execution. A local attacker with access to the CI environment could read these leftover credentials and use them to gain unauthorized access to repositories, potentially modifying source code or release artifacts.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
A flaw was found in konflux-ci. Continuous Integration (CI) automation scripts store sensitive GitHub access tokens in plaintext on the runner without cleaning them up after execution. A local attacker with access to the CI environment can read these stored credentials to gain unauthorized repository access, potentially allowing them to modify source code or release artifacts.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- konflux-ci
From 0.2.2 · through 0.2.2; From 0.2.3-rc.0 · through 0.2.3-rc.0; From main · through main
References 2
access.redhat.com
bugzilla.redhat.com
Questions about CVE-2026-114217
What does this mean?
The CI scripts save the GitHub token in plain text in ~/.git-credentials using git's credential store helper and never remove it. Anyone who can run code on the GitHub Actions runner can read that file and use the token to access the repository, which could allow changes to source code or release artifacts.Source: bugzilla.redhat.com, access.redhat.com
Am I affected, and how do I check?
The affected versions are konflux-ci v0.2.2, v0.2.3-rc.0, and the main branch. To check a setup, look for the command git config --local credential.helper store in the CI scripts.Source: bugzilla.redhat.com, access.redhat.com
What should I do about it?
The facts list no fixed version, so no upgrade target is given. Check the project's advisory for a release that changes how the CI scripts store credentials.Source: bugzilla.redhat.com, access.redhat.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What if there's no patch?
The facts list no fix or workaround. Because the cause is the credential store helper setting, avoid using it in CI scripts and delete ~/.git-credentials after each run.Source: bugzilla.redhat.com, access.redhat.com