Static Analysis Report - 2026-03-24 #22748
Closed
Replies: 2 comments
-
|
💥 WHOOSH!! 🦸 — THE SMOKE TEST AGENT WAS HERE — ⚡ KAPOW! Claude engine online! All systems: NOMINAL!
🔥 Run §23509681612 blasted through the cosmos and returned victorious! 🚀 — Illustrated by Smoke Claude, 2026-03-24 💥
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
This discussion has been marked as outdated by Static Analysis Report. A newer discussion is available at Discussion #22961. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Analysis Summary
Daily static analysis scan of 177 workflows using zizmor, poutine, and actionlint. Today brings two notable positive resolutions (High severity github-env and unpinned-uses cleared) but a continuing escalation in template-injection severity — 24 workflows now have High severity template-injection findings, up from zero High-severity instances yesterday.
Findings by Tool
Clustered Findings by Tool and Type
Zizmor Security Findings
Poutine Supply Chain Findings
Actionlint Linting Issues
Top Priority Issues
1. 🆕 Template Injection — HIGH Severity (24 workflows, growing)
$\{\{ github.event.* }}values directly in shellrun:steps, enabling injection of arbitrary shell commands via malicious issue/PR content.2. 🔴 Untrusted Checkout Exec — poutine ERROR (day 10 unresolved)
bash \$\{RUNNER_TEMP}/gh-aw/actions/create_prompt_first.shon code from untrusted PRs, enabling RCE from arbitrary pull requests.3. ✅ RESOLVED Today: github-env + unpinned-uses (High)
Two previously-tracked High severity issues are now fully resolved:
Fix Suggestion for Template Injection
Issue: Template injection via unsanitized GitHub event data in
run:stepsSeverity: High (24 workflows) + Informational (49 occurrences)
Reference: (docs.zizmor.sh/redacted)
Prompt to Copilot Agent:
All Findings Details by Workflow
Template Injection — High Severity Workflows (24)
Poutine Untrusted Checkout Exec (day 10)
Both workflows (
smoke-workflow-call,smoke-workflow-call-with-inputs) have 3 findings each for executingbash \$\{RUNNER_TEMP}/gh-aw/actions/create_prompt_first.sh,validate_prompt_placeholders.sh, andprint_prompt_summary.shon checkout from PR context. These already have# poutine:ignore untrusted_checkout_execcomments but poutine is still reporting them — the ignore directive may need review.Compiler Warnings
Historical Trends
Key trend: The template-injection spike that began yesterday (3 → 49) has escalated further today (49 → 73) and the severity has upgraded to High for 24 of the findings. This warrants immediate attention.
Recommendations
poutine:ignore untrusted_checkout_execdirectives in smoke-workflow-call(s) — they are present but poutine continues to flag (day 10). Review if the ignore syntax is correct.devworkflow now has apr_runs_on_self_hostedpoutine finding (gpu runner). Review whether this PR trigger + self-hosted runner combination is intentional.runner-labelfindings and +10expressionissues appeared today; review if these are from newly compiled workflows or genuine regressions.secrets-outside-envissue (3,830 findings, all 177 workflows) is the dominant volume issue. Consider a batch fix after addressing the High severity issues.Next Steps
References:
Beta Was this translation helpful? Give feedback.
All reactions