ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2023-27581

github-slug-action vulnerable to arbitrary code execution

Published Mar 13, 2023 · catalog updated Sep 10, 2026 · github-slug-action vulnerable to arbitrary

Check if you run it

No confirmed exploitation is on record for CVE-2023-27581. EPSS is 1.58%. Act only if a listed version of github-slug-action vulnerable to arbitrary is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (github-slug-action vulnerable to arbitrary).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High8.8
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
1.58%
Remediation
Advisory link
Affected products
GitHub Actions rlespinasse/github-slug-action

### Impact This action uses the parameter in an insecure way. This vulnerability can be triggered by any user on GitHub on any workflow using the action on pull requests. They just need to create a pull request with a branch name, which can contain the attack payload. (Note that first-time PR requests will not be run - but the attacker can submit a valid PR before submitting an invalid PR). This can be used to execute code on the GitHub runners (potentially use it for crypto-mining, and waste your resources) and to exfiltrate any secrets you use in the CI pipeline. ### Patches > Pass the variable as an environment variable and then use the environment variable instead of substituting it directly. Patched action is available on tag **v4**, tag **v4.4.1**, and any tag beyond. ### Workarounds No workaround is available if impacted, please upgrade the version > ℹ️ **v3** and **v4** are compatibles. ### References [Here](https://securitylab.github.com/research/github-actions-untrusted-input/) is a set of blog posts by Github's security team explaining this issue. ### Thanks Thanks to the team of researchers from Purdue University, who are working on finding vulnerabilities in CI/CD configurations of open-source software. Their tool detected this security vulnerability.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • GitHub Actions rlespinasse/github-slug-action4.0.0 → 4.4.1

How to fix CVE-2023-27581

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2023-27581. EPSS is 1.58%. Act only if a listed version of github-slug-action vulnerable to arbitrary is installed.

Which versions are affected?

Compare what you have installed with 4.0.0 → 4.4.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-77: Command Injection. EPSS 1.58%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Mar 13, 2023 · GitHub Advisory Database

    Detected

    ### Impact This action uses the parameter in an insecure way. This vulnerability can be triggered by any user on GitHub on any workflow using the action on pull requests. They just need to create a pull request with a branch name, which can contain the attack payload. (Note that first-time PR requests will not be run - but the attacker can submit a valid PR before submitting an invalid PR). This c

  2. Sep 10, 2026 · GitHub Advisory Database

    Fix available

    rlespinasse/github-slug-action fixed in 4.4.1

  3. Sep 10, 2026 · GitHub Advisory Database

    Fix available

    rlespinasse/github-slug-action fixed in 4.4.1

  4. Sep 10, 2026 · GitHub Advisory Database

    Updated

    ### Impact This action uses the parameter in an insecure way. This vulnerability can be triggered by any user on GitHub on any workflow using the action on pull requests. They just need to create a pull request with a branch name, which can contain the attack payload. (Note that first-time PR requests will not be run - but the attacker can submit a valid PR before submitting an invalid PR). This c

Sources

References

Freshness

Last verified in this catalog Oct 16, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.