CVE-2022-39326: kartverket/github-workflows are shared reusable workflows for GitHub Actions

Q: How do I fix CVE-2022-39326?

github-workflows: upgrade to 2.7.5. Exact commands for each OS are on this page.

Q: Is CVE-2022-39326 being exploited?

CVE-2022-39326 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-39326 affect?

CVE-2022-39326 affects github-workflows. Severity is high (CVSS 8.8). kartverket/github-workflows are shared reusable workflows for GitHub Actions. Prior to version 2.7.5, all users of the `run-terraform` reusable workflow from the kartverket/github-workflows repo are affected by a code injection vulnerabilit

This month

HIGH 8.8UPGRADE

CVE-2022-39326 is a high-severity flaw (CVSS 8.8) affecting github-workflows. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

kartverket/github-workflows are shared reusable workflows for GitHub Actions. Prior to version 2.7.5, all users of the `run-terraform` reusable workflow from the kartverket/github-workflows repo are affected by a code injection vulnerability. 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. Users should upgrade to at least version 2.7.5 to reso

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	1.6% (top 24%)
CISA exploited list	No
Weakness	CWE-94
Published	2022-10-25
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: kartverket

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-10-25 17:15 UTCPublished CVE record published
2026-06-17 04:58 UTCUpdated Record last modified

kartverket github-workflows UPGRADE

Affected: < 2.7.5

Fixed in: 2.7.5

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy github-workflows || rpm -q github-workflows || github-workflows --version

2. UPGRADE to 2.7.5 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade github-workflows

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade github-workflows

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-39326?

github-workflows: upgrade to 2.7.5. Exact commands for each OS are on this page.

Is CVE-2022-39326 being exploited?

CVE-2022-39326 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-39326 affect?

CVE-2022-39326 affects github-workflows. Severity is high (CVSS 8.8). kartverket/github-workflows are shared reusable workflows for GitHub Actions. Prior to version 2.7.5, all users of the `run-terraform` reusable workflow from the kartverket/github-workflows repo are affected by a code injection vulnerabilit

How urgent is CVE-2022-39326?

Priority 50/100. High severity

Software pages

GitHub vulnerabilities · Terraform vulnerabilities

References

← Back to latest CVEs