Vulnerability in GitHub Workflow Updater (CVE-2025-62794)
Summary
Vulnerability in GitHub Workflow Updater (CVE-2025-62794). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-62794 has been found in GitHub Workflow Updater.
Risk of unauthorized operations or information disclosure. CVSS score: 3.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "GitHub Workflow Updater CVE-2025-62794" on the vendor's site.
CVE-2025-62794 (GitHub Workflow Updater) — CWE-522 / CVSS v3 3.8
Attack vector: local / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-522) exists in GitHub Workflow Updater.
Check the vendor advisory for the affected versions of GitHub Workflow Updater.
Severity: Low (CVSS 3.8/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで GitHub Workflow Updater を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。