GitHub Agentic Workflows Vulnerable to GitLost Data Leak Exploit
GitHub Agentic Workflows shipped into public preview in February with a pitch that genuinely earned the excitement: skip the automation scripts, write a Markdown file in plain English, hand it to an AI agent powered by GitHub Copilot, Anthropic's Claude, Google Gemini, or OpenAI Codex, and watch it triage issues, run tools, and post comments on its own. No YAML plumbing. No webhook glue. The agent reads the issue, follows your instructions, replies. For teams drowning in triage work, this is the first automation primitive on GitHub that actually feels like delegation.
Then Noma Security researchers published a proof of concept that any external attacker can stand up in an afternoon and use to read your private repositories through the very agent you just delegated to.
This is an excerpt. Read the full post at otf-kit.dev/blog/github-agentic-workflows-vulnerability — full-stack kits your AI coding agent can actually ship to production. Browse the kits →
Ship the product, not the setup.
- 11 production screens — auth, billing, team, analytics, settings
- Real database, payments, and login — all wired on day 1
- AI configs pre-tuned so your agent extends instead of regenerates