dbcve.org
Super LinterApplication · Super Linter Project

CVE-2026-25761

HIGH · 8.8 CVSS v3.1 Published 2026-02-09
Fix available
A fix is available. Upgrade to 8.3.1 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Super-linter GitHub Action versions 6.0.0 through 8.3.0 are vulnerable to command injection via malicious filenames containing shell command substitution syntax like $(...). During file discovery processing, the embedded commands execute in the workflow runner context, potentially exposing the GITHUB_TOKEN.

MitigationUpgrade Super-linter to version 8.3.1 or later in all GitHub Actions workflow files that reference it.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Super LinterApplication
Affected:>= 6.0.0, < 8.3.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate Super-linter workflow references
    Search your repository for .yml or .yaml files in .github/workflows/ that contain 'super-linter' or 'super-linter' in the 'uses' field of a GitHub Action step
    Affected if Files exist that reference super-linter in a workflow
  2. Extract the Super-linter version
    In each workflow file, look for the 'uses' statement (e.g., 'github/[email protected]' or 'github/[email protected]') and record the version number or tag after the '@' symbol
    Affected if A version number or tag is present in the workflow
  3. Compare against vulnerable version range
    Check if the extracted version is >= 6.0.0 AND < 8.3.1. If using a floating tag like 'v6' or 'latest', resolve it to a concrete version by inspecting the GitHub Actions marketplace or repository releases
    Affected if The version is 6.0.0, 6.1.0, 6.2.0, ..., 7.x.x, 8.0.0, 8.1.0, 8.2.0, or 8.3.0
  4. Identify all workflows using vulnerable versions
    Review all workflow files under .github/workflows/ recursively to ensure no instance of Super-linter version 6.0.0-8.3.0 is in use across the entire repository
    Affected if Any workflow file references a version in the vulnerable range

You are affected if any GitHub Actions workflow in your repository uses Super-linter version 6.0.0 through 8.3.0 (including any 8.3.0.x patch version below 8.3.1).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.3.1 or later
Fixed in 8.3.1
Interim mitigation

Upgrade Super-linter to version 8.3.1 or later in all GitHub Actions workflow files that reference it.

Recommended fix High confidence

8.3.1

  1. Locate the GitHub Actions workflow file that uses Super Linter (typically in .github/workflows/ or similar)
  2. Find the version reference for the super-linter action (e.g., uses: github/[email protected] or uses: github/super-linter@v6)
  3. Update the version to 8.3.1 or later (e.g., change @v6 to @v8.3.1 or @v8)
  4. Commit and push the changes to trigger the workflow with the updated version
  5. Verify the workflow runs successfully with the new version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Super Linter Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25761 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-25761 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data