GitHub Actions needs OIDC audience constraints

GitHub Actions exposes a security weakness in its OIDC token mechanism: unlike GitLab CI/CD, which requires the OIDC audience (aud) to be declared statically upfront, GitHub allows workflows to dynamically request tokens with any audience at runtime. This means a job granted id-token: write can mint tokens for any audience, enabling an attacker or malicious third-party dependency to pivot across services (e.g., from a PyPI publishing job to AWS). The proposed fix is an audience constraint syntax in the workflow definition, limiting which audiences a job can request tokens for. This would prevent cross-service token abuse while still allowing a less-secure dynamic fallback for edge cases.

Source: https://blog.yossarian.net/2026/08/10/github-actions-needs-oidc-audience-constraints. 8 Sync News only summarizes and links out; content copyright belongs to the authors and original sources.