GitHub token disclosure via substring hostname validation
Published Jun 9, 2026 · Updated Jun 9, 2026
Credential exposure in Visual Studio Code before 1.123.1 allows remote attackers to steal a signed-in user's GitHub token. The built-in GitHubCredentialProvider accepts attacker-controlled hostnames containing github.com and sends the token via HTTP Basic authentication. Exploitation requires a signed-in user to recursively clone or update submodules from a malicious repository; token scope bounds access to GitHub resources.
Summary
What happened
Credential exposure in Visual Studio Code before 1.123.1 allows remote attackers to steal a signed-in user's GitHub token. The built-in GitHubCredentialProvider accepts attacker-controlled hostnames containing github.com and sends the token via HTTP Basic authentication. Exploitation requires a signed-in user to recursively clone or update submodules from a malicious repository; token scope bounds access to GitHub resources.
The record
- CVE
- CVE-2026-47284
- Published
- Jun 9, 2026
- Updated
- Jun 9, 2026
- Vendor
- Microsoft
- Product
- Visual Studio Code
- Classifications
- CWE-200, T1555
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 9, 2026CVE publishedPublication date reported by the CVE source.
- Jun 9, 2026Record 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=1.0.0 <1.123.1
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