Skip to main content
CVE-2024-8156VulnerabilityPublished Updated

CVE-2024-8156: significant-gravitas/autogpt · Command Injection

Affects significant-gravitas/autogptSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.0 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.7% chance of exploitation in 30 days – higher than 77% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Mar 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
GitHubsignificant-gravitas/autogptpkg:github/significant-gravitas/autogptOther threatsAffected
  • *
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Immediate mitigation steps include disabling or restricting the affected GitHub Actions workflow (workflow-checker.yml) until a secure patch or update is available. Organizations should implement strict validation and sanitization of all untrusted inputs used in workflows, especially branch names and other user-controlled variables. Using GitHub Actions built-in functions or third-party actions that safely handle inputs can reduce risk. Limit the permissions of GitHub Actions runners by adopting the principle of least privilege, including restricting access to secrets and tokens. Employ branch protection rules and require trusted reviewers for pull requests to reduce the risk of malicious branches being merged or triggering workflows. Monitor CI logs and workflow runs for suspicious activity indicative of exploitation attempts. Additionally, consider isolating CI environments and using ephemeral runners to limit persistence of any compromise. Organizations should track updates from the significant-gravitas/autogpt project for official patches and apply them promptly once available.

Description

A command injection vulnerability exists in the workflow-checker.yml workflow of significant-gravitas/autogpt. The untrusted user input `github.head.ref` is used insecurely, allowing an attacker to inject arbitrary commands. This vulnerability affects versions up to and including the latest version. An attacker can exploit this by creating a branch name with a malicious payload and opening a pull request, potentially leading to reverse shell access or theft of sensitive tokens and keys.

References

Community reviews

Loading reviews…