Skip to main content
CVE-2025-62794VulnerabilityPublished

CVE-2025-62794: RichardoC github-workflow-updater-extension · Insufficiently Protected Credentials

Affects RichardoC github-workflow-updater-extensionSource CVE Database V5

0

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

CVSS 3.1 base score
3.8Low
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
GitHubrichardoc/github-workflow-updater-extensionpkg:github/richardoc/github-workflow-updater-extensionOther threatsAffected
  • <0.0.7
Fixed in
  • 0.0.7

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

Community reviews

Loading reviews…