// AI Platform Drift
GitHub detects leaked Cloudflare Access service tokens, disables them automatically
Cloudflare developer changelog · published 2026-11-14 06:28 UTC
WHAT CHANGEDGitHub secret scanning now detects Cloudflare Access service token secrets exposed in public repositories and reports them to Cloudflare. Access disables the affected token immediately and emails account administrators. Service tokens created on or after August 26, 2026 follow a new format: cfast_ followed by 40 alphanumeric characters and an eight-character hexadecimal checksum. Leaked secrets have no rotation grace period—the previous secret is discarded immediately when rotated.
WHY IT MATTERSIf you commit an Access service token to a public repository, it will be disabled without warning, breaking any service using it. The immediate discard on rotation means there is no overlap window to update services—the old secret stops working the moment you rotate.
WHAT TO DOAudit your repositories for Access service tokens using the pattern cfast_[A-Za-z0-9]{40}[a-f0-9]{8} for tokens created after August 26, 2026, or 64-character hexadecimal secrets for legacy tokens. If a token is disabled, rotate it, update all services with the new secret before re-enabling, then re-enable via the API or dashboard.
Model-reported confidence 85% (not measured accuracy)
Primary source ↗
written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Access, Cloudflare One - GitHub automatically detects leaked Access service tokens +https://developers.cloudflare.com/changelog/post/2026-11-11-leaked-service-token-recovery/ +Wed, 11 Nov 2026 00:00:00 GMT + +GitHub secret scanning automatically detects Cloudflare Access service token secrets exposed in public repositories and reports them to Cloudflare. Access then disables the affected token and emails account administrators. +Other secret scanning tools can identify Access service tokens using their consistent Client Secret format: cfast_, followed by 40 alphanumeric characters and an eight-character hexadecimal checksum. For tools that support custom detection rules, use this regular expression to find possible secrets: +cfast_[A-Za-z0-9]{40}[a-f0-9]{8} +This pattern applies to Client Secrets created on or after August 26, 2026, not legacy 64-character hexadecimal secrets. Matching the pattern does not validate the checksum or confirm that the secret is active. For details, refer to Client Secret format. +Recover a leaked service token +Before you can re-enable a leaked token, you must rotate its secret. +Leaked secrets do not support a rotation grace period. When you rotate one, the previous secret is discarded immediately. Update your services with the new secret, then re-enable the token. +For API rotations, omit previous_client_secret_expires_at. A future expiration returns 400. Attempting to re-enable the token before rotation returns 409. + +For recovery steps and leak metadata fields, refer to Recover a leaked service token.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
| triage verdict | MATERIAL at 0.92, needed 0.5 |
|---|---|
| triage reasoning | New security mechanism changes token handling, introduces API constraints, and requires operational changes for affected services. |
| signals | new security feature: automatic token leak detection and disabling · new token format specification with regex pattern · new API behavior: leaked secrets have no rotation grace period · new API error codes: 400 for future expiration, 409 for pre-rotation re-enable · new operational requirement: immediate secret update after rotation · future date: August 26, 2026 marks format change boundary |
| suppression | — |
| triage model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | anthropic/claude-sonnet-4.5 ($0.00000) |