CVE-2025-31479 canonical/get-workflow-version-action can leak a partial GITHUB_TOKEN in exception output

High 8.2 Published Updated

Attackers with repository read access can view partial GITHUB_TOKENs in logs if a step fails, potentially allowing temporary unauthorized access.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2025-31479?

CVE-2025-31479 is a high-severity vulnerability in canonical get-workflow-version-action, published on 2 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

canonical/get-workflow-version-action is a GitHub composite action to get commit SHA that GitHub Actions reusable workflow was called with. Prior to 1.0.1, if the get-workflow-version-action step fails, the exception output may include the GITHUB_TOKEN. If the full token is included in the exception output, GitHub will automatically redact the secret from the GitHub Actions logs. However, the token may be truncated—causing part of the GITHUB_TOKEN to be displayed in plaintext in the GitHub Actions logs. Anyone with read access to the GitHub repository can view GitHub Actions logs. For public repositories, anyone can view the GitHub Actions logs. The opportunity to exploit this vulnerability is limited—the GITHUB_TOKEN is automatically revoked when the job completes. However, there is an opportunity for an attack in the time between the GITHUB_TOKEN being displayed in the logs and the completion of the job. Users using the github-token input are impacted. This vulnerability is fixed in 1.0.1.

Weakness: CWE-532

Which versions are affected by CVE-2025-31479?

1 open source package ship an affected version, including canonical/get-workflow-version-action.

PackageAffectedFixed in
canonical/get-workflow-version-action GitHub ActionsAll versions1.0.1

How do I fix CVE-2025-31479?

Upgrade canonical/get-workflow-version-action to 1.0.1 or later.

Is CVE-2025-31479 being exploited?

There is no known exploitation of CVE-2025-31479 in the wild and no public exploit code.

Sources

Also known as GHSA-26wh-cc3r-w6pj.

Is CVE-2025-31479 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free