Accounts & identity
Pass-the-token
Pass-the-token
Pass-the-token is unauthorised reuse of a valid access token to call a service or API with the rights of a user or application.
Fiche de sensibilisationPrête à diffuser à vos équipes ou clients
MIGHT YOU BE AFFECTED?
Turn knowledge into action.
How does this work?
An access token represents permissions granted to an identity. If exposed in memory, logs, a repository or a compromised endpoint, an attacker may present it to an API without repeating interactive authentication. Whether it works depends on expiry, audience, permissions and any client-binding protections.
REAL-WORLD EXAMPLE
« A cloud access token accidentally included in diagnostic logs is retrieved and used to query an internal API with the associated service permissions. »
Typical sequence
- 1Obtain a valid token from an exposed or compromised source.
- 2Determine the service, audience and permissions of the token.
- 3Present the token to the relevant API.
- 4Read or modify resources within its granted scope.
- 5Attempt to establish persistence through other credentials.
Warning signs
- API calls from an unfamiliar environment.
- Token use outside expected hours or context.
- Unusual request volume or bulk exports.
- Tokens or secrets exposed in logs or repositories.
- Access without a corresponding interactive sign-in.
How to protect yourself
- Limit token scope and lifetime, and revoke stolen bearer tokens.
- Never log or publish access tokens.
- Use short lifetimes and least-privilege scopes.
- Restrict service-account permissions.
- Protect endpoints and application secrets.
- Detect abnormal API access.
- Use supported token-binding mechanisms when available.
If you think you are affected
Revoke affected tokens, determine whether linked sessions or keys also require rotation, and eliminate the exposure path. Investigate API calls, accessed resources and any unauthorised changes.
Last updated: 8 October 2026