Skip to content

GitHub now flags leaked Cloudflare Access service tokens automatically

Cloudflare and GitHub secret scanning now detect exposed Access service tokens in public repos and disable them on sight. Recovery needs a full rotation, with no grace period.

GitHub’s secret scanning now recognises Cloudflare Access service tokens, which follow a consistent format: cfast_, 40 alphanumeric characters, then an 8-character hex checksum. When GitHub finds one exposed in a public repository, it reports it to Cloudflare, which disables the token and emails the account’s administrators.

The catch is in recovery. A token flagged this way can’t just be re-enabled. Cloudflare requires a full secret rotation first, and leaked secrets get no grace period: the moment you rotate, the old secret stops working immediately, everywhere it’s used. Trying to re-enable before rotating returns a 409. Organisations running their own secret scanning can use the same regex, cfast_[A-Za-z0-9]{40}[a-f0-9]{8}, to catch leaks before GitHub does.

cfast_[A-Za-z0-9]{40}[a-f0-9]{8}

Why it matters: if a service token ends up in a public commit, you no longer get to quietly re-enable it and carry on. Every system that holds that token needs the new secret before you flip it back on, so know which services use it before this happens to you, not after.

Share

Related reading

More from The Wire

All briefs