{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-26493 exists.","fix":"No fix has been published for CVE-2023-26493 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-26493 is a high-severity command injection vulnerability in cocos-engine, published on 27 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-26493 and fix it if it is affected.\n\nWhat it is: CVE-2023-26493 is a high-severity command injection vulnerability in cocos-engine, published on 27 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-26493 exists.\n\nAffected product: cocos-engine. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-26493/ (Markdown: https://insights.sbomify.com/CVE-2023-26493/index.md)","id":"CVE-2023-26493","markdown":"https://insights.sbomify.com/CVE-2023-26493/index.md","name":"CVE-2023-26493","record":{"aliases":[],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Cocos Engine CI workflow","requires_auth":"low_privilege","summary":"Attackers could inject commands via pull request branch names in Cocos Engine's CI workflow to execute code and steal secrets.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"cocos-engine","vendor":"cocos"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-77","name":"Improper Neutralization of Special Elements used in a Command"},{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"Cocos Engine is an open-source framework for building 2D \u0026 3D real-time rendering and interactive content. In the github repo for Cocos Engine the `web-interface-check.yml` was subject to command injection. The `web-interface-check.yml` was triggered when a pull request was opened or updated and contained the user controllable field `(${{ github.head_ref }} – the name of the fork’s branch)`. This would allow an attacker to take over the GitHub Runner and run custom commands (potentially stealing secrets such as GITHUB_TOKEN) and altering the repository. The workflow has since been removed for the repository. There are no actions required of users.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-08-31","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-08-31T13:53:42Z","kind":"github_poc","ref":"https://github.com/pvharmo2/gha-lab-fb32aba4a3","stars":0,"title":"Authorized lab reproduction of CVE-2023-26493 (GHSL-2023-027): command injection via github.head_ref in cocos-engine's \u003cWeb\u003e Interface check pull_request_target workflow"}],"tier":"weaponised"},"has_fix":false,"headline":"Command Injection in Cocos Engine workflow","id":"CVE-2023-26493","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"lorawan-stack has open redirect vulnerability","id":"CVE-2023-26494"},"packages":[],"prev":{"headline":"Directus vulnerable to Server-Side Request Forgery On File Import","id":"CVE-2023-26492"},"products":["cocos-engine"],"published":"2023-03-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-02-19","vendors":["cocos"]},"summary":"Attackers could inject commands via pull request branch names in Cocos Engine's CI workflow to execute code and steal secrets.","url":"https://insights.sbomify.com/CVE-2023-26493/"}