{"answers":{"affected":"1 open source package ship an affected version, including tj-actions/branch-names.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54416 exists.","fix":"Upgrade tj-actions/branch-names to 9.0.0 or later.","what":"CVE-2025-54416 is a critical command injection vulnerability in tj-actions branch-names, published on 26 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-54416 and fix it if it is affected.\n\nWhat it is: CVE-2025-54416 is a critical command injection vulnerability in tj-actions branch-names, published on 26 Jul 2025. 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-2025-54416 exists.\n\nAffected packages and fixed versions:\n- tj-actions/branch-names (GitHub Actions): affected all versions; fixed in 9.0.0\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-2025-54416/ (Markdown: https://insights.sbomify.com/CVE-2025-54416/index.md)","id":"CVE-2025-54416","markdown":"https://insights.sbomify.com/CVE-2025-54416/index.md","name":"CVE-2025-54416","record":{"aliases":["GHSA-gq52-6phf-x2r6"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"GitHub Actions","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary commands in downstream workflows via crafted branch names in the tj-actions/branch-names GitHub Action.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-77","name":"Improper Neutralization of Special Elements used in a Command"}],"description":"tj-actions/branch-names is a Github actions repository that contains workflows to retrieve branch or tag names with support for all events. In versions 8.2.1 and below, a critical vulnerability has been identified in the tj-actions/branch-names' GitHub Action workflow which allows arbitrary command execution in downstream workflows. This issue arises due to inconsistent input sanitization and unescaped output, enabling malicious actors to exploit specially crafted branch names or tags. While internal sanitization mechanisms have been implemented, the action outputs remain vulnerable, exposing consuming workflows to significant security risks. This is fixed in version 9.0.0","ecosystems":["GitHub Actions"],"exploits":{"exploitdb":0,"first_seen":"2026-04-13","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-04-13T16:02:48Z","kind":"github_poc","ref":"https://github.com/HexborneStudio/atlas-tj-actions-poc","stars":0,"title":"PoC for CVE-2025-54416 tj-actions/branch-names command injection"}],"tier":"weaponised"},"has_fix":true,"headline":"tj-actions/branch-names Contains Command Injection Vulnerability","id":"CVE-2025-54416","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"GitHub Actions","product":null,"products":[],"type":"command_injection","year":"2025"},"n_packages":1,"n_references":3,"next":{"headline":"Craft contains a theoretical bypass for CVE-2025-23209","id":"CVE-2025-54417"},"packages":[{"ecosystem":"GitHub Actions","fixed":["9.0.0"],"introduced":["0"],"last_affected":[],"package":"tj-actions/branch-names","purl":null,"source":"GHSA-gq52-6phf-x2r6"}],"prev":{"headline":"dag-factory's CI/CD Workflow Allows for Repository Takeover and Secret Exfiltration","id":"CVE-2025-54415"},"products":["branch-names"],"published":"2025-07-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"partial"},"state":"PUBLISHED","updated":"2025-07-28","vendors":["tj-actions"]},"summary":"Attackers can execute arbitrary commands in downstream workflows via crafted branch names in the tj-actions/branch-names GitHub Action.","url":"https://insights.sbomify.com/CVE-2025-54416/"}