Super Linter
Approved changes feed: RSS · Atom
cpe:2.3:a:super-linter:super-linter:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Super Linter (53c2211b-e4f4-596d-b591-275f5c0f1907) |
|---|---|
| Product | Super Linter (a313ad44-a4e7-5791-8c53-84b7c8533530) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-25761 |
vulnerable | 2026-06-08 07:53:20.311607 |
Command injection via crafted filenames in Super-linter Action
HIGH (8.8)
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.
Published: 2026-02-09T20:27:01.887Z
Updated: 2026-02-10T15:59:33.745Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.