Playbooks · Coding tasks
Secret scanning now catches Cloudflare Access tokens
Written November 13, 2026
GitHub secret scanning added a detector for Cloudflare Access service tokens on November 12. What it catches, and where the alerts land.
What changed
GitHub's changelog for November 12, 2026 says secret scanning now detects Cloudflare service tokens. The new secret type is named cloudflare_access_service_token. One detector, one token family: the Access service tokens that Cloudflare services use to authenticate to applications protected by Cloudflare Access.
These tokens are easy to leak in the ordinary way — a client secret pasted into a config file, a test fixture, or an example that turns out to hold a real value — and until now this pattern was not one of the types GitHub scanning knew by name.
What happens when it fires
The changelog entry draws the standard distinction for this detector class. Partner secrets are automatically reported to the secret issuer when found in public repositories, through the secret scanning partnership program. User secrets generate secret scanning alerts when found in public or private repositories.
For this token type, the issuer side of that loop is concrete. Cloudflare's own changelog says GitHub scanning detects Access service token secrets exposed in public repositories and reports them to Cloudflare, and that Access then disables the affected token and emails account administrators. A leak in a public repository does not sit waiting for someone to triage an alert: the token is switched off and the admins hear about it.
Recovery means rotation, with no grace period
Cloudflare's recovery notes set the terms for getting back. Before a leaked token can be re-enabled, its secret must be rotated. Leaked secrets do not support a rotation grace period: when you rotate one, the previous secret is discarded immediately. Services using the token need the new secret in place, and only then can the token be re-enabled. An API rotation that tries to keep the old secret alive for a while is refused, and trying to re-enable the token before rotating it is refused as well.
That ordering is the part to plan around. Anything calling through that Access token stops working when the token is disabled, and it stays stopped until the rotation and the service updates are done. The recovery is short, but it is a hard cut, not an overlap.
The pattern other tools can use
Cloudflare publishes the shape of the secret so other scanners can look for it too. Access service token client secrets created on or after August 26, 2026 use a consistent format: the prefix cfast_, followed by 40 alphanumeric characters and an eight-character hexadecimal checksum. Cloudflare gives a regular expression for tools that support custom detection rules. Two cautions come with it: the pattern does not cover the older 64-character hexadecimal secrets, and matching the pattern does not validate the checksum or confirm that a secret is active.
Where this leaves a team
For most teams, nothing needs installing: the detector joins the scanning that GitHub already runs, and its effect shows up only when a matching secret appears. The preparation worth doing is procedural. Make sure the people who would receive a Cloudflare admin email about a disabled token know what it means and who owns the rotation, so a disabled production token is a short incident with a known owner rather than a mystery outage traced back, eventually, to a commit.
What to do
- Search your repositories for committed Access service token secrets, including older hexadecimal-format secrets the new pattern does not describe.
- If a token of yours is disabled after a public leak, rotate first, update the services that use it, then re-enable — in that order.
- Where you run other scanners, add the published pattern as a custom rule, knowing its August 26, 2026 scope limit.
Related playbooks
- Secret scanning now catches Actions log leaks
- Check whether your Claude Code hooks are adding tokens to every prompt or cutting them
- Cloudflare runs the Codex loop in a Durable Object
- Two gh-aw advisories: tokens and temp files
Sources
- Secret scanning detects Cloudflare service tokens — GitHub Changelog
- GitHub automatically detects leaked Access service tokens — Cloudflare Changelog
Back to: Coding tasks playbooks hub · Also: Secret scanning now catches Actions log leaks