Super-linter up to 8.3.0 GITHUB_TOKEN command injection

Summaryinfo

A vulnerability identified as critical has been detected in Super-linter up to 8.3.0. Impacted is an unknown function. The manipulation of the argument GITHUB_TOKEN leads to command injection. This vulnerability is listed as CVE-2026-25761. The attack may be initiated remotely. There is no available exploit. You should upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Super-linter up to 8.3.0. This issue affects some unknown functionality. The manipulation of the argument GITHUB_TOKEN with an unknown input leads to a command injection vulnerability. Using CWE to declare the problem leads to CWE-77. The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Super-linter is a combination of multiple linters to run as a GitHub Action or standalone. From 6.0.0 to 8.3.0, the Super-linter GitHub Action is vulnerable to command injection via crafted filenames. When this action is used in downstream GitHub Actions workflows, an attacker can submit a pull request that introduces a file whose name contains shell command substitution syntax, such as $(...). In affected Super-linter versions, runtime scripts may execute the embedded command during file discovery processing, enabling arbitrary command execution in the workflow runner context. This can be used to disclose the job’s GITHUB_TOKEN depending on how the workflow configures permissions. This vulnerability is fixed in 8.3.1.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-25761 since 02/05/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1202 for this issue.

Upgrading to version 8.3.1 eliminates this vulnerability. The upgrade is hosted for download at github.com.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Super-linter

Version

• 8.0
• 8.1
• 8.2
• 8.3.0

Website

• Product: https://github.com/super-linter/super-linter/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion