AIToday
Large Language ModelsAI Safety & AlignmentZenn AI/MLPublished: Oct 13, 2026, 10:00 JST

Vulnerability Busters: AI security agent that waits for human approval

Vulnerability Busters: AI security agent that waits for human approval

3 Key Points

  1. What happened

    A developer entered the 5th Agentic AI Hackathon with Google Cloud with "Vulnerability Busters," which scans a demo Cloud Run app, has Gemini plan fixes, then re-scans to confirm what actually disappeared.

  2. Why it matters

    The agent can't change production on its own, so small teams without a dedicated security person may find a way to fix and verify vulnerabilities without handing an AI unchecked control.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

The project was built for the 5th Agentic AI Hackathon with Google Cloud, and the developer framed it as an answer to a specific problem: vulnerability work is important but easy to postpone because the loop of reading results, fixing, deploying, and verifying rarely gets finished.

The design pairs a game interface with real security operations, so the visible "deletion" of a vulnerability is produced only from the re-scan results, not from the AI's own claim of success. This reflects a broader pattern in the submission: the AI decides how to fix, but the human decides whether production changes happen, and the scanner decides whether the fix worked.

The developer also lists what is not finished: multi-user support, and cloud-side per-component updates, since the cloud deployer does not build, leaving base-image replacement as the main RUNTIME fix path. A plan exists to add a fixed-form tool for selecting package names and versions.

FAQ
Who is this tool meant for?
It is aimed at small teams running services on Cloud Run that do not have a dedicated security person, according to the project description.
Can the AI deploy fixes on its own?
No. The AI plans fixes and runs dry runs, but a human must approve deployment, and the approval is bound to the specific fix revision.
How does it decide a vulnerability was fixed?
After deployment, the same scanner re-scans; only detections that actually disappear are counted as deleted, while new issues surface as NEW RISK.

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleEpic's $1.5 billion Disney shooter goes "AI first"