wrdn-gha-workflows

Identify exploitable GitHub Actions workflow defects from untrusted data in privileged contexts.

56|3|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/getsentry/warden-skills --skill wrdn-gha-workflows
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrdn-gha-workflows
Source: https://github.com/getsentry/warden-skills/tree/main/skills/wrdn-gha-workflows
Command: npx skills add https://github.com/getsentry/warden-skills --skill wrdn-gha-workflows

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps security reviewers identify and trace exploitable GitHub Actions workflows where attacker-controlled inputs reach privileged steps, enabling code execution, secret leakage, or runner compromise.

Core Features & Use Cases

  • Trace risks across .github/workflows, action.yml, and reusable workflows to map end-to-end exploit chains.
  • Provide structured findings with entry points, inputs, sinks, and remediation guidance for PRs, workflow_call, and workflow_dispatch scenarios.
  • Use documented references to distinguish safe patterns from exploit patterns and to calibrate severity.

Quick Start

Review the repository's workflows to surface exploitable input-to-sink chains and suggest concrete hardening steps.

Frequently Asked Questions about wrdn-gha-workflows

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect expression injection vulnerabilities in GitHub Actions workflows?

Detect GitHub Actions workflow vulnerabilities by tracing untrusted data from triggers like pull_request_target to privileged contexts. Map end-to-end exploit chains where attacker-controlled inputs reach steps, enabling code execution or secret leakage. Structured findings include entry points, sinks, and remediation guidance.

What makes a GitHub Actions workflow exploitable through pull_request_target?

A GitHub Actions workflow is exploitable through pull_request_target when untrusted pull request data flows into privileged steps without proper trust boundaries. This allows attacker-controlled inputs to influence commands or secrets, enabling code execution or credential exposure during the workflow run.

How do I audit reusable workflows for supply-chain security risks?

Audit reusable workflows for supply-chain risks by evaluating workflow_call and workflow_dispatch triggers, inputs, and sinks. Trace how inputs influence commands, secrets, or tokens across single-repo and reusable-callee scenarios to identify exploitable defects and suggest concrete hardening steps.

Does this workflow audit approach work with reusable workflows triggered by workflow_call and workflow_dispatch?

Yes, this workflow audit approach evaluates workflows triggered by workflow_call and workflow_dispatch where inputs can influence commands, secrets, or tokens. It assesses trust boundaries and step boundaries across both single-repo and reusable-callee scenarios to produce structured findings.

What are the limitations of detecting GitHub Actions security defects automatically?

Detecting GitHub Actions security defects requires evaluating triggers, trust boundaries, inputs, and sinks across single-repo and reusable-callee scenarios. It focuses on untrusted data reaching privileged contexts but relies on documented references to distinguish safe patterns from exploit patterns and calibrate severity accurately.