Authenticated command execution via unsafe eval printf
Published Jul 26, 2025 · Updated Jul 28, 2025
Command injection in tj-actions Branch Names 8.2.1 and earlier allows remote authenticated users to execute commands through crafted refs. The composite action passes printf-escaped branch and tag values through eval printf before writing outputs, which reinterprets shell metacharacters. A repository workflow must consume an affected action output after an attacker-controlled branch or tag triggers it; resulting commands run with the runner token and available secrets.
Summary
What happened
Command injection in tj-actions Branch Names 8.2.1 and earlier allows remote authenticated users to execute commands through crafted refs. The composite action passes printf-escaped branch and tag values through eval printf before writing outputs, which reinterprets shell metacharacters. A repository workflow must consume an affected action output after an attacker-controlled branch or tag triggers it; resulting commands run with the runner token and available secrets.
The record
- CVE
- CVE-2025-54416
- Published
- Jul 26, 2025
- Updated
- Jul 28, 2025
- Vendor
- tj-actions
- Product
- Branch Names
- Classifications
- CWE-77, T1059.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 26, 2025CVE publishedPublication date reported by the CVE source.
- Jul 28, 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=< 9.0.0
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
- Crafted branch-name 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