How to fix: Heroku API Key Exposed
Heroku API key pattern found.
Why it matters
Full Heroku account control.
Heroku keys allow app deployment and deletion.
How to fix it
- 1Regenerate API key immediately.
Code examples
Revoke exposed Heroku API key
# Revoke at: dashboard.heroku.com > Account Settings > API Key > Reveal + Regenerate
# Or via CLI:
heroku auth:whoami
heroku auth:logout
# Log in again to get a new session token
# For CI: use Heroku API keys as env vars in your CI platform
# Never commit them to source codeReferences
Detected automatically by VulnRadar. The check id is heroku-api-key-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 Heroku API Key Exposed?
- 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 heroku-api-key-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Heroku API Key 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.