You change an endpoint and forget to check which organization the record belongs to. Vercel says logic flaws like a missing authorization check are exactly what pattern-matching scanners miss. On 2 November the company launched Security Review in public beta. It checks on every push, and only the change.
Fact
The facts: on 2 November 2026 Vercel announced Vercel Security Review in public beta. It is a new capability in Vercel Agent, alongside Code Review and Investigation. Once enabled, it scans for vulnerabilities on every push to a team's connected GitHub repositories. Findings appear as comments on pull requests, in the Security dashboard and via CLI. As examples of what it catches, Vercel names missing authorization checks and exposed secrets. Each review compares the push against a base and covers only the changed code; for deployments the base is the branch's previous deployment. Because of that, in Vercel's words, the review finishes in seconds. On private and internal repositories it also adds a GitHub check to the commit and comments on the pull request. Policies are written in plain language, and the CLI commands are vercel security policy and vercel security vulnerabilities. When fixing, the agent confirms the vulnerability still exists, makes the smallest change that fixes it and updates the tests. It is available to Pro and Enterprise teams. Pricing is at the Vercel Agent rate, with model tokens at the provider's rate and no markup, plus $0.25 per million tokens. Security reviews are free until 10 November 2026, and fixes made with Vercel Agent are billed.
The price is more complicated than it looks. Only the reviews are free, and only until 10 November 2026. Fixes with the agent are billed from day one. What the Vercel Agent rate actually is, the blog does not say.
The table of findings in the same blog is for a fictional team, and the invoice code is a made-up example. The blog has no real measurement of this check. How many findings it catches on real code and how many false alarms it raises, the page does not say.
The review looks at the change, not the whole repository.
For now it works only with code pushed to GitHub. Vercel announces the next steps as a plan: deployments from the Vercel CLI and v0, repositories that do not deploy on Vercel, and suggested fixes straight from the pull request.
If you are on Pro or Enterprise, turn it on in Vercel Agent Settings for one project and look at the first findings on your own code. That way you can judge whether it is worth it before 10 November 2026 passes.
Official primary sources
Vercel - Introducing Vercel Security Review, 02.11.2026The visual is generated code-art, no third-party images.