Token disclosure via plaintext editor configuration
Published Oct 28, 2025 · Updated Oct 28, 2025
Insufficient credential protection in GitHub Workflow Updater before 0.0.7 allows local users to read a GitHub token from disk. The extension registers github-workflow-updater.githubToken as an application-scoped string setting, causing VS Code to serialize the token into its JSON settings instead of SecretStorage. Read access to the affected user’s home directory exposes the token and permits GitHub actions within its granted permissions.
Summary
What happened
Insufficient credential protection in GitHub Workflow Updater before 0.0.7 allows local users to read a GitHub token from disk. The extension registers github-workflow-updater.githubToken as an application-scoped string setting, causing VS Code to serialize the token into its JSON settings instead of SecretStorage. Read access to the affected user’s home directory exposes the token and permits GitHub actions within its granted permissions.
The record
- CVE
- CVE-2025-62794
- Published
- Oct 28, 2025
- Updated
- Oct 28, 2025
- Vendor
- RichardoC
- Product
- GitHub Workflow Updater
- Classifications
- CWE-522, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 28, 2025CVE publishedPublication date reported by the CVE source.
- Oct 28, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.0.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo