← All permissions
Repository permission·id_token:write
OIDC ID token: Write
Tier 1 · High
Why Tier 1
Lets the job request an OIDC token and trade it for cloud credentials. The cloud trust policy is the only check left; a wildcard subject turns this into cloud admin.
Data plane permissions start at Tier 2. This one is raised for the reason above.
Context-dependent: the tier shown is the typical case. What the target is used for decides the real one.
- Target
- Repository
- Plane
- DataSecrets: Actions, environment, Dependabot, Codespaces and agent secrets, private registries and OIDC.
- Granted by
- GITHUB_TOKEN
- Available on
- Every setup
- In a workflow
permissions: id-token: write
Roles that include it
No built-in role includes it. Only tokens, Apps or custom roles can grant it.
Classic scopes that reach it
No classic scope reaches it. Only fine-grained PATs, Apps or GITHUB_TOKEN can grant it.
Attack paths
Techniques it enables
- Run PR code in a privileged workflow Steal CI secrets and tokens
Reached through
- Change a workflow, get its secrets · from Workflows: Write