Security risks associated with GitHub Actions cache
Publication date is supplied by the source. Prepared by Cybermonit · Content updated:
AI summary
A pull request from a fork can restore a cache from the base branch, so an attacker may read cached data without access to repository secrets. The risk grows when cached paths include home directories holding Docker or AWS CLI tokens. According to HackRead, many such secrets stay valid for years, though that is a general statement, not a measured finding. The report recommends avoiding broad cache directories, using OpenID Connect for temporary credentials and requiring manual approval for external contributors' workflows. The article relays HackRead's report, gives no incidents or CVE identifiers, and does not say whether GitHub changed its default behavior.
