Skip to main content
CriticalSecretsOWASP A07:2021CWE-798

How to fix: Linode API token in source

Linode personal access tokens (64-char hex) grant Linode account takeover including instance termination.

Why it matters

An exposed Linode personal access token gives full API control over your Linode account: an attacker can terminate running instances, create new ones to mine cryptocurrency at your expense, access managed databases, and read or delete your stored data.

Linode personal access tokens (64-char hex) grant Linode account takeover including instance termination.

How to fix it

  1. 1Revoke the token at cloud.linode.com → Profile → API Tokens
  2. 2Generate a new token with minimum required permissions and a short expiry
  3. 3Store new tokens in a secrets manager, not in code or environment variables

Code examples

Revoke Linode token via API

bash
# List personal access tokens to find the compromised one
curl -H 'Authorization: Bearer YOUR_TOKEN' \
  'https://api.linode.com/v4/profile/tokens'

# Revoke the token (replace TOKEN_ID with the ID from the list)
curl -X DELETE \
  -H 'Authorization: Bearer YOUR_TOKEN' \
  'https://api.linode.com/v4/profile/tokens/TOKEN_ID'

References

Detected automatically by VulnRadar. The check id is secret-linode-api-key, stable across every scan so you can filter or diff on it.

See every secrets check

Questions

How severe is Linode API token in source?
VulnRadar rates this critical severity in the secrets 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 secret-linode-api-key, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Linode API token in source 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.

Propose a checkHow a check is built

Scan your own site for linode api token in source

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: Linode API token in source | VulnRadar