conflibot GitHub Action Vulnerability: Command Injection via Branch Names
- Severity
- HIGH
- Affected component
- conflibot (github-actions)
- Affected versions
- < 1.2.1
- Patched version
- 1.2.1
An early warning has been issued regarding a vulnerability in the conflibot GitHub Action. Versions before 1.2.1 are reportedly susceptible to command injection through crafted pull request branch names.
What happened
The conflibot GitHub Action, utilized in software workflows, has been identified as vulnerable to command injection. This vulnerability, tracked as GHSA-2QVG-QR73-MQXP, allows for the execution of arbitrary commands on the runner when pull request branch names are specially crafted. Versions of conflibot prior to 1.2.1 are affected. The issue was first flagged on August 17, 2026, and is currently under investigation. It is recommended to review your usage of conflibot and assess your exposure to this vulnerability.
This supply-chain attack vector is particularly concerning as it can be triggered through the pull_request_target event, a common mechanism in GitHub Actions workflows. The vulnerability has not been reported as exploited in the wild, but the potential impact is high due to the nature of command injection attacks.
What to do about it
- Immediately upgrade to conflibot@v2.0.0 or v1.2.1 to mitigate the vulnerability.
- Review your GitHub Actions workflows for any usage of conflibot and ensure they are updated to a secure version.
- Monitor the GitHub Advisory Database and other primary sources for updates on this vulnerability.
- Consider implementing additional security measures for your GitHub Actions workflows to prevent similar vulnerabilities.
How 0Day would have caught this
conflibot is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.
Frequently asked questions
Am I affected?
If you are using conflibot in versions before 1.2.1, you are potentially affected by this vulnerability.
What should I do right now?
Upgrade to conflibot@v2.0.0 or v1.2.1 to protect your workflows from this vulnerability.
Has this vulnerability been exploited in the wild?
There are no reports of this vulnerability being exploited in the wild at this time.
Where can I find more information about this vulnerability?
Consult the GitHub Advisory Database and the primary sources listed for the most up-to-date information.