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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.2 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:H

EPSS

• CVE-2025-31479: 0.60% estimated exploitation activity in the next 30 days; percentile 48.48 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Users using the github-token input are impacted. If the get-workflow-version-action step fails, the exception output may include the GITHUBTOKEN. 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 GITHUBTOKEN 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 GITHUBTOKEN is automatically revoked when the job completes. However, there is an opportunity for an attack in the time between the GITHUBTOKEN being displayed in the logs and the completion of the job. Normally this is less than a second, but it may be greater if continue-on-error is used in the get-workflow-version-action step or if status check functions are used in a later step…

Published by the source

2 Apr 2025, 22:36 UTC

Last modified by the source

3 Apr 2025, 13:26 UTC

Source last checked

26 Oct 2026, 17:08 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-26wh-cc3r-w6pj

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-31479

Advisory: canonical/get-workflow-version-action can leak a partial GITHUB_TOKEN in exception output
IDs: CVE-2025-31479, GHSA-26wh-cc3r-w6pj
Record: https://patchnext.com/advisories/cve-2025-31479 (revision 1, source checked 26 Oct 2026, 17:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: canonical/get-workflow-version-action 1.0.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- GitHub Actions canonical/get-workflow-version-action: affected < 1.0.1; fixed in 1.0.1

## Suggested inspection (read-only)
- GitHub Actions canonical/get-workflow-version-action: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on canonical/get-workflow-version-action.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-26wh-cc3r-w6pj (GitHub-reviewed advisory GHSA-26wh-cc3r-w6pj lists affected ranges: GitHub Actions canonical/get-workflow-version-action >=0 <1.0.1)

Commands are suggestions: review each one before running it.