Skip to main content
No exploitation reportedFix available

CVE-2026-25761

No exploitation reported by the sources we read.

  • Published2026-02-09
  • Fixed in8.3.1
  • WeaknessCWE-77

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2026-02-0921:15CVE publishedNVD

Versions per branch

NVD · OSV
Super-linter project super-linter
BranchAffectedFixed in
8.3≥ 6.0.0, < 8.3.18.3.1

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • super-linter
    Affected
    • = >= 6.0.0, < 8.3.1no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-02-09

Fix

  1. Update Super-linter project super-linter to 8.3.1

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVE recordread 2026-10-23
  • CISA-ADPSSVC decisionnone2026-02-10
  • CNACVSS 3.18.8known since 2026-10-23
  • CNAweakness (CWE)CWE-77known since 2026-10-23
  • FIRST EPSSEPSS score1.5 %2026-11-18
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryHIGH2026-02-09

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Published
2026-02-09
Last Modified
2026-06-17
NVD status
Analyzed
GitHub Advisory
GHSA-r79c-pqj3-577x

Frequently asked questions

What is CVE-2026-25761?

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.

Is CVE-2026-25761 actively exploited?

Active exploitation of CVE-2026-25761 has not been confirmed. Its EPSS score was 1.5% on 2026-11-18, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-25761?

CVE-2026-25761 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.

Running super-linter/super-linter? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record