code-review-cicd
Review CI/CD pipelines for security flaws — poisoned workflows, secret leakage, and injection. Load on GitHub Actions / GitLab CI / Jenkins config, ".github/workflows", pull_request_target, self-hosted runners, or "pipeline security". Signals: workflow YAML, secrets in CI, third-party actions.
v2026.10.14-ee0e0c53 installs+3 in 7 days27 StarsMITsynced 23 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/code-review-cicdWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package5fa743f1…d80f089b
5fa743f192bc…1049d80f089b1 file · 1.5 KBScanLowno findings
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/code-review/code-review-cicd@ee0e0c5
On this page
When it applies
You can read a repo's CI config (GitHub Actions, GitLab CI, Jenkinsfile, CircleCI). Pipelines run with secrets and often on attacker-influenced input (PRs), making them a high-value, under-reviewed target.
Why it works
CI runs code with privileged tokens/secrets. Misconfigurations let a fork PR run in a trusted context, inject commands via untrusted inputs, or exfiltrate secrets — a supply-chain foothold. On public repos this can be exploitable by anyone who opens a PR.
Method
- Dangerous triggers:
pull_request_target/workflow_runthat check out and run PR code with secrets in scope → fork PRs can steal secrets or run arbitrary code (the classic GitHub Actions bug). - Script injection: untrusted data (
github.event.issue.title, PR body, branch name) used directly inrun:shells → command injection. Look for${{ github.event.* }}inrunblocks. - Secret handling: secrets echoed/logged, passed to third-party actions, or available to fork PRs;
overly broad
permissions:(defaultwrite), long-livedGITHUB_TOKEN. - Untrusted dependencies: third-party actions pinned to a mutable tag/branch (not a SHA), curl-pipe-to-shell steps, unpinned package installs → supply-chain.
- Self-hosted runners on public repos: fork PRs executing on your infra → RCE on the runner.
Gotchas
pull_request(safe-ish) vspull_request_target(dangerous) — the trigger name is the crux.- An action pinned to
@v3(tag) can be moved; require a full commit SHA for third-party actions. - Secret leakage often happens via a step passing
${{ secrets.X }}to an untrusted action.
Verify success
A concrete path where an outsider (fork PR / issue) can execute code with pipeline privileges or exfiltrate a secret, or a clear secret-leak/injection in the workflow.
References
GitHub Actions security hardening docs; "GitHub Actions pwn requests" (Nathan Davison); semgrep CI rules.
Files in this version
- SKILL.md2.6 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
The scan found nothing to flag in this version.
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | Nov 13, 2026 | ee0e0c5 | 5fa743f1 | Signed | – |
More from NoorQureshi
All from this publisherMore in Web and bug bounty
See the category- src-hunterzhaoxuya520/src-hunter5
- owasp-top10-analysissecurityskills/owasp-top10-analysis5
- testing-for-xml-injection-vulnerabilitiesmukul975/testing-for-xml-injection-vulnerabilities5
- offensive-xsssnailsploit/offensive-xss5
- offensive-rcesnailsploit/offensive-rce5
- source-review-techniqueaeondave/source-review-technique5
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login