How to fix: GitHub Token Pattern Detected
GitHub personal access token found.
Why it matters
Repository access, code manipulation.
GitHub tokens grant repo access.
How to fix it
- 1Revoke token immediately, use fine-grained tokens.
Code examples
Revoke exposed GitHub token immediately
# Revoke at: github.com/settings/tokens
# Check recent activity:
curl -H "Authorization: token TOKEN" https://api.github.com/user
curl -H "Authorization: token TOKEN" https://api.github.com/users/OWNER/events
# Replace with a fine-grained token scoped to specific repos
# Or use GitHub Actions GITHUB_TOKEN (auto-scoped, expires after run)References
Detected automatically by VulnRadar. The check id is github-token-exposed, stable across every scan so you can filter or diff on it.
More content checks
- MediumPotential Open Redirect Parameters
- HighDirectory Listing Appears Enabled
- MediumSensitive File References Detected
- HighPotentially Outdated JavaScript Libraries
- Inforobots.txt Present - Review Manually
- InfoCMS / Technology Fingerprinting
- MediumPotentially Dangerous Inline JavaScript
- LowServer version disclosed in response header
Questions
- How severe is GitHub Token Pattern Detected?
- VulnRadar rates this critical severity in the content category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id github-token-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does GitHub Token Pattern Detected map to?
- It maps to CWE-798. In the OWASP Top 10 it falls under A07:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.