# CVE-2026-25761: Command injection via crafted filenames in Super-linter Action

> Attackers can execute arbitrary commands in GitHub Actions runners via crafted filenames, potentially exposing secrets like GITHUB_TOKEN.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 9 Feb 2026
- **Updated:** 10 Feb 2026
- **Also known as:** GHSA-r79c-pqj3-577x

## What is CVE-2026-25761?

CVE-2026-25761 is a high-severity command injection vulnerability in super-linter, published on 9 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2026-25761?

2 open source packages ship an affected version, including super-linter/super-linter and super-linter/super-linter/slim. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `super-linter/super-linter` | GitHub Actions | From 6.0.0 | 8.3.1 |
| `super-linter/super-linter/slim` | GitHub Actions | From 6.0.0 | 8.3.1 |

Products: Super-Linter Project Super-Linter.

## How do I fix CVE-2026-25761?

Upgrade super-linter/super-linter to 8.3.1 or later.

## Is CVE-2026-25761 being exploited?

There is no known exploitation of CVE-2026-25761 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25761 and fix it if it is affected.

What it is: CVE-2026-25761 is a high-severity command injection vulnerability in super-linter, published on 9 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-25761 in the wild and no public exploit code.

Affected packages and fixed versions:
- super-linter/super-linter (GitHub Actions): affected from 6.0.0; fixed in 8.3.1
- super-linter/super-linter/slim (GitHub Actions): affected from 6.0.0; fixed in 8.3.1

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-25761/ (Markdown: https://insights.sbomify.com/CVE-2026-25761/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25761
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25761
- OSV: https://osv.dev/vulnerability/CVE-2026-25761

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-25761/
Summaries are generated and may contain mistakes; the official description above is the record.