High [CVE-2026-87049] Over-permissive GITHUB_TOKEN and GCP WIF secrets granted to third-party reusable workflow on untrusted-triggerable events
This high-severity Red Hat Linux advisory covers CVE-2026-87049.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
Over-permissive GITHUB_TOKEN and GCP WIF secrets granted to third-party reusable workflow on untrusted-triggerable events. Red Hat rates this important (CVSS 8.7).
Weakness: CWE-269.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 8 hours ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 8 hours ago·verify at source
Mitigation checklist
- To mitigate this vulnerability, restrict GitHub Actions workflow permissions by moving broad `permissions:` blocks from the workflow level to specific jobs, pruning them to the minimum required. Pin third-party reusable workflows to a full 40-character commit SHA instead of a version tag. Implement author-association checks (OWNER/MEMBER/COLLABORATOR) or maintainer-applied labels for jobs triggered by untrusted events (e.g., `pull_request_target`, `issue_comment`) that receive `id-token: write` or repository secrets. Additionally, configure the GCP Workload Identity Federation provider's attribute condition to only accept tokens from protected-branch workflow runs.
Official advisory · high-confidence parse· fetched 8 hours ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.