How severe is GHSA-f9qj-7gh3-mhj4?

GHSA-f9qj-7gh3-mhj4 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-f9qj-7gh3-mhj4?

GHSA-f9qj-7gh3-mhj4 affects the following packages: kartverket/github-workflows (GitHub Actions). Ecosystems affected: GitHub Actions.

How do I fix GHSA-f9qj-7gh3-mhj4?

Update kartverket/github-workflows to 2.7.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f9qj-7gh3-mhj4 is resolved across your whole dependency graph.

How do I detect GHSA-f9qj-7gh3-mhj4 in my GitHub Actions dependencies?

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

How do I mitigate GHSA-f9qj-7gh3-mhj4 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is GHSA-f9qj-7gh3-mhj4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-f9qj-7gh3-mhj4 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-f9qj-7gh3-mhj4?

GHSA-f9qj-7gh3-mhj4 has an EPSS (Exploit Prediction Scoring System) score of 1.6%, placing it in the 77th 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-f9qj-7gh3-mhj4?

GHSA-f9qj-7gh3-mhj4 is classified as Code Injection (CWE-94). 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-f9qj-7gh3-mhj4 published, and has it been updated?

GHSA-f9qj-7gh3-mhj4 was published on October 19, 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

Not in CISA KEV

HIGH severity

run-terraform allows for RCE via terraform planGHSA-f9qj-7gh3-mhj4

HIGHFix: kartverket/github-workflows#19

GHSA-f9qj-7gh3-mhj4 is a high-severity (CVSS 8.8) Code Injection vulnerability in kartverket/github-workflows. A fix is available for kartverket/github-workflows — see the affected versions and patch details below.

Also known asCVE-2022-39326

Published

Oct 19, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-f9qj-7gh3-mhj4.

EPSS Exploitation Probability

via FIRST.org ↗

1.6%probability of exploitation in next 30 days

Lower Risk+0.32%

Lower risk than most CVEs77th percentile — riskier than 77% 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

📦kartverket/github-workflows

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

What kind of vulnerability is it? Who is impacted?
All users of the run-terraform reusable workflow from the kartverket/github-workflows repo are affected. A malicious actor could potentially send a PR with a malicious payload leading to execution of arbitrary JavaScript code in the context of the workflow.

Patches

Has the problem been patched? What versions should users upgrade to?
Upgrade to at least 2.7.5 to resolve the issue.

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?
Until you are able to upgrade, make sure to review any PRs from exernal users for malicious payloads before allowing them to trigger a build.

For more information

If you have any questions or comments about this advisory:

Open an issue in kartverket/github-workflows

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦GitHub Actions	`kartverket/github-workflows`	all versions	2.7.5

Affected Products

1 product · 1 configurations

Application

github-workflowskartverket

< 2.7.5

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for kartverket/github-workflows, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update kartverket/github-workflows to 2.7.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f9qj-7gh3-mhj4 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

### Impact _What kind of vulnerability is it? Who is impacted?_ All users of the `run-terraform` reusable workflow from the kartverket/github-workflows repo are affected. A malicious actor could potentially send a PR with a malicious payload leading to execution of arbitrary JavaScript code in the context of the workflow. ### Patches _Has the problem been patched? What versions should users upgrade to?_ Upgrade to at least 2.7.5 to resolve the issue. ### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ Until you are able to upgrade, make s