Runner takeover via unquoted pull-request branch name
Published Mar 27, 2023 · Updated Feb 19, 2025
Command injection in Cocos Engine before 6d06aefa26 allows remote authenticated users to execute commands on a GitHub Actions runner. The web-interface-check.yml workflow inserts the pull request's attacker-controlled head_ref branch name into git fetch and git merge shell commands without neutralization. Opening or updating a fork-based pull request triggers the write-token workflow, enabling repository modification and workflow-secret theft.
Summary
What happened
Command injection in Cocos Engine before 6d06aefa26 allows remote authenticated users to execute commands on a GitHub Actions runner. The web-interface-check.yml workflow inserts the pull request's attacker-controlled head_ref branch name into git fetch and git merge shell commands without neutralization. Opening or updating a fork-based pull request triggers the write-token workflow, enabling repository modification and workflow-secret theft.
The record
- CVE
- CVE-2023-26493
- Published
- Mar 27, 2023
- Updated
- Feb 19, 2025
- Vendor
- Cocos
- Product
- Cocos Engine
- Classifications
- CWE-77, CWE-74, T1059.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 27, 2023CVE publishedPublication date reported by the CVE source.
- Feb 19, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 6d06aefa26
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Fork branch-name command-injection proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo