How severe is GHSA-2c6m-6gqh-6qg3?

GHSA-2c6m-6gqh-6qg3 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-2c6m-6gqh-6qg3?

GHSA-2c6m-6gqh-6qg3 affects the following packages: actions/runner (GitHub Actions), actions/runner (GitHub Actions), actions/runner (GitHub Actions), actions/runner (GitHub Actions), actions/runner (GitHub Actions). Ecosystems affected: GitHub Actions.

How do I fix GHSA-2c6m-6gqh-6qg3?

Update actions/runner to 2.296.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2c6m-6gqh-6qg3 is resolved across your whole dependency graph.

How do I detect GHSA-2c6m-6gqh-6qg3 in my GitHub Actions dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for actions/runner. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-2c6m-6gqh-6qg3 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-2c6m-6gqh-6qg3?

O3 pinpoints whether GHSA-2c6m-6gqh-6qg3 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-2c6m-6gqh-6qg3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-2c6m-6gqh-6qg3 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-2c6m-6gqh-6qg3?

GHSA-2c6m-6gqh-6qg3 has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 70th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-2c6m-6gqh-6qg3?

GHSA-2c6m-6gqh-6qg3 is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-2c6m-6gqh-6qg3 published, and has it been updated?

GHSA-2c6m-6gqh-6qg3 was published on October 25, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 GitHub Actions

GHSA-2c6m-6gqh-6qg3

HIGH

Docker Command Escaping in the GitHub Actions Runner

Also known asCVE-2022-39321

Published

Oct 25, 2022

Updated

Nov 8, 2023

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk70th percentile+0.52%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

5 pkgs affected

📦actions/runner📦actions/runner📦actions/runner📦actions/runner📦actions/runner

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects GitHub Actions packages — download data is not available via public APIs for these ecosystems.

Description

Impact

The actions runner invokes the docker cli directly in order to run job containers, service containers, or container actions. A bug in the logic for how the environment is encoded into these docker commands was discovered that allows an input to escape the environment variable and modify that docker command invocation directly. Jobs that use container actions, job containers, or service containers alongside untrusted user inputs in environment variables may be vulnerable.

Patches

The Actions Runner has been patched, both on github.com and hotfixes for GHES and GHAE customers. Please update to one of the following versions of the runner:

2.296.2
2.293.1
2.289.4
2.285.2
2.283.4

GHES and GHAE customers may want to patch their instance in order to have their runners automatically upgrade to these new runner versions.

Workarounds

You may want to consider removing any container actions, job containers, or service containers from your jobs until you are able to upgrade your runner versions.

For more information

If you have any questions or comments about this advisory:

Open an issue in the actions runner

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
📦GitHub Actions	`actions/runner`	≥ 2.294.0&&< 2.296.2	2.296.2
📦GitHub Actions	`actions/runner`	≥ 2.290.0&&< 2.293.1	2.293.1
📦GitHub Actions	`actions/runner`	≥ 2.286.0&&< 2.289.4	2.289.4
📦GitHub Actions	`actions/runner`	≥ 2.284.0&&< 2.285.2	2.285.2
📦GitHub Actions	`actions/runner`	all versions	2.283.4

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for actions/runner. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update actions/runner to 2.296.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2c6m-6gqh-6qg3 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-2c6m-6gqh-6qg3 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-2c6m-6gqh-6qg3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact The actions runner invokes the docker cli directly in order to run job containers, service containers, or container actions. A bug in the logic for how the environment is encoded into these docker commands was discovered that allows an input to escape the environment variable and modify that docker command invocation directly. Jobs that use [container actions](https://docs.github.com/en/actions/creating-actions/creating-a-docker-container-action), [job containers](https://docs.github.com/en/actions/using-jobs/running-jobs-in-a-container), or [service containers](https://docs.github

O3 Security · Impact-Aware SCA

Is GHSA-2c6m-6gqh-6qg3 in your dependencies?

O3 detects GHSA-2c6m-6gqh-6qg3 across GitHub Actions dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-2c6m-6gqh-6qg3

EPSS Exploitation Probability

Blast Radius

Description

Impact

Patches

Workarounds

For more information

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is GHSA-2c6m-6gqh-6qg3 in your dependencies?