Workflow command execution via crafted filenames
Published Feb 9, 2026 · Updated Feb 9, 2026
Command injection in Super-Linter 6.0.0 through 8.3.0 allows remote attackers to execute commands through crafted pull-request filenames. The BuildFileList function passes git ls-tree filenames through sh -c and eval during repository file discovery without neutralizing shell syntax. Exploitation requires a workflow that runs the action on an attacker-controlled pull request without administrator approval; commands run as the workflow runner and can read exposed GITHUB_TOKEN values.
Summary
What happened
Command injection in Super-Linter 6.0.0 through 8.3.0 allows remote attackers to execute commands through crafted pull-request filenames. The BuildFileList function passes git ls-tree filenames through sh -c and eval during repository file discovery without neutralizing shell syntax. Exploitation requires a workflow that runs the action on an attacker-controlled pull request without administrator approval; commands run as the workflow runner and can read exposed GITHUB_TOKEN values.
The record
- CVE
- CVE-2026-25761
- Published
- Feb 9, 2026
- Updated
- Feb 9, 2026
- Vendor
- Super-Linter
- Product
- Super-Linter
- Classifications
- CWE-77, T1059.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 9, 2026CVE publishedPublication date reported by the CVE source.
- Feb 9, 2026Record 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=>= 6.0.0, < 8.3.1
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
No public exploit references are available in this record.
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