{"answers":{"affected":"1 open source package ship an affected version, including canonical/get-workflow-version-action.","exploited":"There is no known exploitation of CVE-2025-31479 in the wild and no public exploit code.","fix":"Upgrade canonical/get-workflow-version-action to 1.0.1 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2025-31479 and fix it if it is affected.\n\nWhat it is: 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.\nExploitation: There is no known exploitation of CVE-2025-31479 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- canonical/get-workflow-version-action (GitHub Actions): affected all versions; fixed in 1.0.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-31479/ (Markdown: https://insights.sbomify.com/CVE-2025-31479/index.md)","id":"CVE-2025-31479","markdown":"https://insights.sbomify.com/CVE-2025-31479/index.md","name":"CVE-2025-31479","record":{"aliases":["GHSA-26wh-cc3r-w6pj"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"GitHub Actions","requires_auth":"low_privilege","summary":"Attackers with repository read access can view partial GITHUB_TOKENs in logs if a step fails, potentially allowing temporary unauthorized access.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"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.","ecosystems":["GitHub Actions"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"canonical/get-workflow-version-action can leak a partial GITHUB_TOKEN in exception output","id":"CVE-2025-31479","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"GitHub Actions","product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":1,"n_references":3,"next":{"headline":"aiven-extras allows PostgreSQL Privilege Escalation through format function","id":"CVE-2025-31480"},"packages":[{"ecosystem":"GitHub Actions","fixed":["1.0.1"],"introduced":["0"],"last_affected":[],"package":"canonical/get-workflow-version-action","purl":null,"source":"GHSA-26wh-cc3r-w6pj"}],"prev":{"headline":"Zulip Authentication Backend Configuration Bypass","id":"CVE-2025-31478"},"products":["get-workflow-version-action"],"published":"2025-04-02","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-03","vendors":["canonical"]},"summary":"Attackers with repository read access can view partial GITHUB_TOKENs in logs if a step fails, potentially allowing temporary unauthorized access.","url":"https://insights.sbomify.com/CVE-2025-31479/"}