CVE-2025-62794: RichardoC github-workflow-updater-extension · Insufficiently Protected Credentials
Affects RichardoC github-workflow-updater-extensionSource CVE Database V5
Not known to be exploited · CVSS 3.8 Low : upgrade to 0.0.7 when convenient.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.0.7
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade richardoc/github-workflow-updater-extension to 0.0.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubrichardoc/github-workflow-updater-extensionpkg:github/richardoc/github-workflow-updater-extensionOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should ensure all developers and DevOps personnel update the github-workflow-updater-extension to version 0.0.7 or later immediately. Additionally, implement endpoint security measures to restrict unauthorized access to user home directories, including enforcing strong user authentication, limiting local user privileges, and deploying host-based intrusion detection systems. Regularly audit and monitor access to developer workstations for suspicious activity. Encourage the use of multi-factor authentication (MFA) on GitHub accounts to reduce the impact of token compromise. Educate developers about secure credential storage practices and the risks of storing tokens in plaintext. Consider integrating secrets management solutions that centralize and secure tokens rather than relying on local storage. Finally, review and rotate GitHub tokens periodically to limit the window of opportunity for attackers.
Description
GitHub Workflow Updater is a VS Code extension that automatically pins GitHub Actions to specific commits for enhanced security. Before 0.0.7, any provided Github token would be stored in plaintext in the editor configuration as json on disk, rather than through the more secure "securestorage" api. An attacker with read only access to your home directory could have read this token and used it to perform actions with that token. Update to 0.0.7.
References
- github.com/RichardoC/github-workflow-updater-extension/security/advisories/GHSA-679x-97jw-8vjp (opens in a new tab)
- github.com/RichardoC/github-workflow-updater-extension/commit/b9518c38ac6bc2a9fda2242e6daef17f7184ad1f (opens in a new tab)
- github.com/microsoft/vscode-discussions/discussions/748 (opens in a new tab)