How severe is GHSA-4xqx-pqpj-9fqw?

GHSA-4xqx-pqpj-9fqw has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-4xqx-pqpj-9fqw?

GHSA-4xqx-pqpj-9fqw affects the following packages: atlassian/gajira-create (GitHub Actions). Ecosystems affected: GitHub Actions.

How do I fix GHSA-4xqx-pqpj-9fqw?

Update atlassian/gajira-create to 2.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4xqx-pqpj-9fqw is resolved across your whole dependency graph.

How do I detect GHSA-4xqx-pqpj-9fqw in my GitHub Actions dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for atlassian/gajira-create, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-4xqx-pqpj-9fqw 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.

Is GHSA-4xqx-pqpj-9fqw actively exploited in the wild?

No public exploit code has been indexed for GHSA-4xqx-pqpj-9fqw 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-4xqx-pqpj-9fqw?

GHSA-4xqx-pqpj-9fqw has an EPSS (Exploit Prediction Scoring System) score of 2.9%, placing it in the 87th 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.

When was GHSA-4xqx-pqpj-9fqw published, and has it been updated?

GHSA-4xqx-pqpj-9fqw was published on October 7, 2022 and was last updated on September 10, 2026. 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

Not in CISA KEV

CRITICAL severity

gajira-create GitHub action vulnerable to arbitrary code executionGHSA-4xqx-pqpj-9fqw

CRITICAL

GHSA-4xqx-pqpj-9fqw is a critical-severity (CVSS 9.8) remote code execution vulnerability in atlassian/gajira-create. A fix is available for atlassian/gajira-create — see the affected versions and patch details below.

Also known asCVE-2020-14188

Published

Oct 7, 2022

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs87th percentile — riskier than 87% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

📦atlassian/gajira-create

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

An attacker can execute arbitrary code in the context of a GitHub runner by creating a specially crafted GitHub issue.

Patches

This issue is patched in gajira-create version 2.0.1.

Workarounds

There are no known workarounds.

References

GitHub Security Lab advisory GHSL-2020-172

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦GitHub Actions	`atlassian/gajira-create`	all versions	2.0.1

Affected Products

1 product · 1 configurations

Application

jira createatlassian

< 2.0.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for atlassian/gajira-create, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update atlassian/gajira-create to 2.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4xqx-pqpj-9fqw 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.

Frequently Asked Questions

### Impact An attacker can execute arbitrary code in the context of a GitHub runner by creating a specially crafted GitHub issue. ### Patches This issue is patched in gajira-create version 2.0.1. ### Workarounds There are no known workarounds. ### References [GitHub Security Lab advisory GHSL-2020-172](https://securitylab.github.com/advisories/GHSL-2020-172-gajira-create-action)

O3 Security · Impact-Aware SCA

Is GHSA-4xqx-pqpj-9fqw in your dependencies?

Find it across GitHub Actions, including transitive dependencies.

Scan my dependencies How O3 SCA works

gajira-create GitHub action vulnerable to arbitrary code executionGHSA-4xqx-pqpj-9fqw

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Impact

Patches

Workarounds

References

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-4xqx-pqpj-9fqw in your dependencies?