How to fix: Docker Hub Token Exposed
Docker Hub credentials found.
Why it matters
Container image manipulation.
Docker tokens allow image push/pull.
How to fix it
- 1Regenerate token immediately.
Code examples
Revoke exposed Docker Hub token
# Revoke at: hub.docker.com > Account Settings > Security > Access Tokens
# Create a new token with minimum required permissions (Read-only for pull)
# In CI: use DOCKER_HUB_TOKEN as a secret env var
docker login -u "$DOCKER_HUB_USER" -p "$DOCKER_HUB_TOKEN"
# For private registries, consider ECR or GHCR with OIDC (no long-lived tokens)References
Detected automatically by VulnRadar. The check id is docker-hub-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 Docker Hub Token Exposed?
- VulnRadar rates this high 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 docker-hub-token-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Docker Hub Token Exposed 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.