CVE-2025-31479
canonical/get-workflow-version-action can leak a partial GITHUB_TOKEN in exception output
In short
A GitHub Actions tool can accidentally expose part of a security token (GITHUB_TOKEN) in error messages if something goes wrong. Even though GitHub tries to hide these tokens automatically, this one might get cut off and show in plain text, allowing anyone who can see the logs to potentially misuse it.
Technical detail
CWE-532 (Log Injection) vulnerability where the get-workflow-version-action composite action may leak a partial GITHUB_TOKEN in exception output when the action fails. The attack vector requires read access to GitHub Actions logs (automatic for public repositories); the truncated token bypasses GitHub's automatic redaction mechanism. Impact is limited by token auto-revocation at job completion, but exploitation is possible during the job execution window.
Summary generated and translated by AI from the 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.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:H