Skip to content

chore(deps): update super-linter/super-linter action to v8.3.1 [security]#56

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/github-tags-super-linter-super-linter-vulnerability
Open

chore(deps): update super-linter/super-linter action to v8.3.1 [security]#56
renovate[bot] wants to merge 1 commit intomainfrom
renovate/github-tags-super-linter-super-linter-vulnerability

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Mar 1, 2026

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change
super-linter/super-linter action minor v8.0.0v8.3.1

GitHub Vulnerability Alerts

CVE-2026-25761

Summary

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.

Details

The issue appears originates in the logic that scans the repository for changed files to check.

  1. Use a workflow that runs Super-linter on pull_request events.
  2. Open a pull request that adds a new file with a crafted filename containing command substitution and an outbound request that includes $GITHUB_TOKEN.
  3. Run the workflow.

Impact

  • Arbitrary command execution in the context of the workflow run that invokes Super-linter (triggered by attacker-controlled filenames in a PR).
  • Credential exposure / misuse: the injected command can read environment variables available to the action, including GITHUB_TOKEN.

The level of exposure depends on the source of the pull request.

To actively exploit the vulnerability, an attacker needs have the ability to run workflows without any approval from the repository admin.

Also, the GITHUB_TOKEN needs to have unconstrained access to repository resources. Even in that case, for pull request coming from forked repositories, no secrets are passed to the forked repository when running workflows triggered by pull_request events, and the GITHUB_TOKEN drops and write permission on the source repository source.

Finally, although not specific to this vulnerability, we recommend auditing workflow_call and pull_request_target workflows because they can lead to compromise, regardless of whether you're using Super-linter, or not, as explained by this GitHub Enterprise doc.

Severity
  • CVSS Score: 8.8 / 10 (High)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Release Notes

super-linter/super-linter (super-linter/super-linter)

v8.3.1

Compare Source

🐛 Bugfixes
⬆️ Dependency updates
🧰 Maintenance

v8.3.0

Compare Source

🚀 Features
🐛 Bugfixes
⬆️ Dependency updates
🧰 Maintenance

v8.2.1

Compare Source

🐛 Bugfixes
⬆️ Dependency updates
  • docker: bump the docker group with 2 updates (#​7100) (28c5681)
  • npm: bump eslint from 9.36.0 to 9.37.0 in /dependencies (#​7102) (cf6cb1e)
  • npm: bump renovate from 41.132.2 to 41.136.0 in /dependencies (#​7107) (495692f)
  • npm: bump the eslint-plugins-configs group across 1 directory with 2 updates (#​7101) (b3a735d)
  • npm: bump the npm group across 1 directory with 4 updates (#​7108) (ce227b3)
  • npm: bump typescript (#​7109) (deba11c)
  • python: bump the pip group across 1 directory with 7 updates (#​7106) (7c02a56)
🧰 Maintenance

v8.2.0

Compare Source

🚀 Features
🐛 Bugfixes
⬆️ Dependency updates
🧰 Maintenance

v8.1.0

Compare Source

🚀 Features
⬆️ Dependency updates

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • ""
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/github-tags-super-linter-super-linter-vulnerability branch 3 times, most recently from 5d34fbc to 6f70f26 Compare March 2, 2026 11:09
@renovate renovate bot changed the title chore(deps): update super-linter/super-linter action to v8.3.1 [security] chore(deps): update super-linter/super-linter action to v8.3.1 [security] - autoclosed Mar 27, 2026
@renovate renovate bot closed this Mar 27, 2026
@renovate renovate bot deleted the renovate/github-tags-super-linter-super-linter-vulnerability branch March 27, 2026 03:04
@renovate renovate bot changed the title chore(deps): update super-linter/super-linter action to v8.3.1 [security] - autoclosed chore(deps): update super-linter/super-linter action to v8.3.1 [security] Mar 30, 2026
@renovate renovate bot reopened this Mar 30, 2026
@renovate renovate bot force-pushed the renovate/github-tags-super-linter-super-linter-vulnerability branch 2 times, most recently from 6f70f26 to 88fc856 Compare March 30, 2026 20:04
@renovate renovate bot force-pushed the renovate/github-tags-super-linter-super-linter-vulnerability branch from 88fc856 to 2f0760b Compare April 12, 2026 10:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants