Konflux-ci: remote code execution via eval() in manifest scripts
- 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
Konflux-ci, a software supply chain tool used in CI/CD pipelines, is affected. An attacker with write access to a repository could run arbitrary commands in the build environment, potentially stealing authentication tokens and deployment credentials and gaining access to production systems.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
A flaw was found in konflux-ci. An attacker with repository write access can achieve arbitrary code execution within the Continuous Integration and Continuous Delivery (CI/CD) workflow environment. By injecting shell commands into environment export scripts, the attacker causes manifest synchronization scripts to dynamically evaluate unvalidated script output. Successful exploitation allows the attacker to compromise CI/CD pipelines, steal sensitive authentication tokens and deployment credentials, and gain unauthorized access to production systems.
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
References 2
access.redhat.com
bugzilla.redhat.com
Questions about CVE-2026-116964
What does this mean?
An attacker who has write access to the repository can run arbitrary code inside the CI/CD workflow environment through eval() in the manifest synchronization scripts. That environment can expose tokens, deployment credentials, and potentially production systems.Source: bugzilla.redhat.com, access.redhat.com
Am I affected, and how do I check?
The product ranges list konflux-ci 0.2.2 and 0.2.3-rc.0, each as a single affected version, and the advisory also names the main branch of Konflux CI as affected (verified 2026-09-20). The issue applies to Konflux CI GitHub Actions workflows that run the manifest synchronization scripts. To check, compare the konflux-ci version in use and whether it is a main-branch build against those versions.Source: bugzilla.redhat.com, access.redhat.com
What should I do about it?
The checked facts do not name a fixed version, so no upgrade target can be given. Watch the Konflux CI project for a release that is later than the affected versions and move to it once it is published.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 checked facts list no workaround. Because the attack requires repository write access, restricting who holds write access to the repository is the only lever the facts support.Source: bugzilla.redhat.com, access.redhat.com