Research · 116 days ago

YAML Anchors Exposed Blind Spots in GitHub Workflow Scanning

zizmor’s old anchor handling did more than miss a corner case. It created analyzer blind spots in valid GitHub Actions workflows, so a clean scan could still leave pull_request_target misconfigurations untested. That matters because the recent Trivy supply-chain exploit showed how those workflow mistakes turn into secret theft and downstream compromise.

Trail of Bits and the zizmor maintainers added full YAML anchor support, fixed parsing and deserialization bugs, and aligned the expression evaluator with GitHub’s tests. They validated the changes against 41,253 real workflows from 6,612 high-value repositories, and the work closed crashes and wrong-location findings that affected anchor-using files.

Timeline

• May 22 Reported by Trail of Bits

Sources

1 source covering this story

• Trail of Bits May 22

  We hardened zizmor's GitHub Actions static analyzer

  We improved YAML anchor support in zizmor and tested it against 41,253 real-world GitHub Actions workflows from high-value open-source projects.

Part of the PlainSec briefing for 2026-05-22

Editions

• Briefing for 2026-05-22

Related stories

• GitHub Actions Became a Secret-Stealing Conveyor Belt