{"vulnerability": "CVE-2025-31479", "sightings": [{"uuid": "5f07cbb7-3e70-4642-9466-303272abd149", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-31479", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114270632021246470", "content": "", "creation_timestamp": "2025-04-02T22:04:31.238733Z"}, {"uuid": "f0f8164e-2a55-4360-b031-feba5eb32cae", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-31479", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114270632021246470", "content": "", "creation_timestamp": "2025-04-02T22:04:31.252184Z"}, {"uuid": "3ab6ac38-db7a-4da4-a167-c884f39a47e6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-31479", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lluikupzg52k", "content": "", "creation_timestamp": "2025-04-02T23:01:23.816841Z"}, {"uuid": "d60f82af-ba76-4cba-b238-2c646e97b47b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-31479", "type": "seen", "source": "https://mastodon.social/users/CyberSignaler/statuses/114271041132793130", "content": "", "creation_timestamp": "2025-04-02T23:48:33.462365Z"}, {"uuid": "0530a1f9-6318-4417-84d4-fa2f2274ce8a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-31479", "type": "seen", "source": "https://mastodon.social/users/CyberSignaler/statuses/114271041132793130", "content": "", "creation_timestamp": "2025-04-02T23:48:33.467381Z"}, {"uuid": "dff02805-8166-46b0-9493-73767f64423a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-31479", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/10144", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-31479\n\ud83d\udd25 CVSS Score: 8.2 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:H)\n\ud83d\udd39 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\u2014causing 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\u2014the 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.\n\ud83d\udccf Published: 2025-04-02T21:09:34.354Z\n\ud83d\udccf Modified: 2025-04-02T21:09:34.354Z\n\ud83d\udd17 References:\n1. https://github.com/canonical/get-workflow-version-action/security/advisories/GHSA-26wh-cc3r-w6pj\n2. https://github.com/canonical/get-workflow-version-action/issues/2\n3. https://github.com/canonical/get-workflow-version-action/commit/88281a62e96e1c0ef4df30352ae0668a9f3e3369", "creation_timestamp": "2025-04-02T21:34:13.000000Z"}, {"uuid": "754088e6-2279-459c-933f-ec8dea5200ce", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-31479", "type": "seen", "source": "https://t.me/cvedetector/21917", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-31479 - GitHub Get-Workflow-Version-Action Token Truncation Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-31479 \nPublished : April 2, 2025, 10:15 p.m. | 20\u00a0minutes ago \nDescription : 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\u2014causing 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\u2014the 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. \nSeverity: 8.2 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"03 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-03T01:01:24.000000Z"}]}