CVE-2025-31479 Details
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.
A vulnerability exists in the Canonical Get-Workflow-Version-Action GitHub composite action, specifically in versions prior to 1.0.1. This action retrieves the commit SHA associated with a reusable workflow in GitHub Actions. The vulnerability arises when the action fails, as the exception output may inadvertently include a partial GITHUB_TOKEN. While GitHub automatically redacts the full token from the logs, a truncated version can be exposed in plaintext. This issue affects anyone with read access to the repository, and for public repositories, the logs are accessible to everyone. Although the GITHUB_TOKEN is revoked at the end of the job, there is a brief window of opportunity for exploitation, particularly if 'continue-on-error' is used or if certain status check functions are applied in the workflow.
Users of the Canonical Get-Workflow-Version-Action should update to version 1.0.1. If a GITHUB_TOKEN was leaked while using version 1.0.0, it should have been revoked automatically, but users should be aware of the potential for exploitation if the token was used before it was revoked.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Apr 2, 2025CISA-ADP
Assessed Apr 3, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/canonical/get-workflow-version-action/commit/88281a62e96e1c0ef4df30352ae0668a9f3e3369 | [email protected] | Source CodeVendor |
| https://github.com/canonical/get-workflow-version-action/issues/2 | [email protected] | Issue TrackingTechnical DescriptionVendor |
| https://github.com/canonical/get-workflow-version-action/security/advisories/GHSA-26wh-cc3r-w6pj | [email protected] | AdvisoryRemedyVendor |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-532 | Insertion of Sensitive Information into Log File | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| canonical/get-workflow-version-action | All versions |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Apr 2, 2025 | New CVE Received | [email protected] |
Volerion