Skip to main content
CriticalContentOWASP A07:2021CWE-798

How to fix: Private Key Detected in Source

Private key pattern found in page.

Why it matters

Complete compromise of encrypted data.

Private keys should never be in HTML.

How to fix it

  1. 1Rotate keys, investigate how they were exposed.

Code examples

Revoke and replace exposed private keys

bash
# For TLS certificates: contact your CA to revoke the cert immediately
# openssl genrsa -out new_private.key 4096
# Then reissue the certificate with the new key

# For JWT signing keys: rotate and invalidate all existing tokens
# For SSH keys: remove from authorized_keys on all servers

# Store new private keys in a KMS or secrets manager, never in source

References

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

See every content check

Questions

How severe is Private Key Detected in Source?
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 private-key-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Private Key Detected 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 private key detected 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: Private Key Detected in Source | VulnRadar