---
type: "post"
id: "we-have-automatically-applied-waf-protections-for-vercel-609afc"
slug: "we-have-automatically-applied-waf-protections-for-vercel-609afc"
title: "We have automatically applied WAF protections for Vercel users."
description: "Better Auth released versions 1.7.16 and 1.8.0-beta.5 to address 12 security advisories across authentication, sessions, authorization, and billing."
retrieval_nugget: "Better Auth released versions 1.7.16 and 1.8.0-beta.5 to address 12 security advisories across authentication, sessions, authorization, and billing. Vercel says it has deployed free WAF rules for hosted projects, but affected applications still need patched packages and, in some cases, credential rotation or data cleanup."
published_at: "2026-11-04"
updated_at: "2026-11-04"
record_date: "2026-11-04"
date_kind: "published_at"
topics: ["agent-security"]
entities: ["Vercel","Better Auth","@better-auth/expo"]
related_patterns: ["agent-security-moves-to-runtime-boundaries"]
novelty_label: "new_fact"
what_changed: "Vercel says it deployed free WAF rules to automatically protect projects against the Better Auth vulnerabilities; no listed prior covers this bulletin."
prior_refs: []
source_url: "https://vercel.com/kb/bulletin/better-auth-november-2026-security-release"
source_urls: ["https://vercel.com/kb/bulletin/better-auth-november-2026-security-release"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:we-have-automatically-applied-waf-protections-for-vercel-609afc"
status: "published"
visuals: []
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/we-have-automatically-applied-waf-protections-for-vercel-609afc/","markdown":"https://newruntime.com/posts/we-have-automatically-applied-waf-protections-for-vercel-609afc.md","json":"https://newruntime.com/posts/we-have-automatically-applied-waf-protections-for-vercel-609afc.json"}
markdown_url: "https://newruntime.com/posts/we-have-automatically-applied-waf-protections-for-vercel-609afc.md"
---

# We have automatically applied WAF protections for Vercel users.

## Retrieval answer

Better Auth released versions 1.7.16 and 1.8.0-beta.5 to address 12 security advisories across authentication, sessions, authorization, and billing. Vercel says it has deployed free WAF rules for hosted projects, but affected applications still need patched packages and, in some cases, credential rotation or data cleanup.

## Summary
Better Auth released versions 1.7.16 and 1.8.0-beta.5 to address 12 security advisories across authentication, sessions, authorization, and billing. Vercel says it has deployed free WAF rules for hosted projects, but affected applications still need patched packages and, in some cases, credential rotation or data cleanup.

## What happened
The Better Auth team shipped a coordinated security release addressing 12 advisories. The affected areas include authentication bypass, account takeover, session revocation, authorization checks, and billing. The patched versions listed by Vercel are Better Auth 1.7.16 and 1.8.0-beta.5, both available on npm. The bulletin identifies one critical issue in `@better-auth/expo`, rated CVSS 9.1: an authorization proxy could sign values it did not issue. If the vulnerable Expo endpoint was reachable, Vercel says to rotate the application secret after upgrading. If SSO sign-in then stops working, the identity provider's origin may need to be added to `trustedOrigins`.

Other advisories call for more than a package update. A high-severity phone-number issue allowed numbers to be claimed before verification; on version 1.7.16, previously saved numbers whose verification was incomplete should be removed, requiring those users to add them again. The beta version additionally checks account ownership before verifying pending numbers, including numbers stored before upgrade. A separate Electron issue could return the server secret and bypass two-factor authentication. If an affected Electron server plugin was running, Vercel advises assuming the authentication secret and configured social-provider client secrets were exposed and rotating all of them. An upgrade cannot reverse a disclosure that already happened.

The medium-severity list includes email-change links that remain valid after an address changes hands, OAuth treating an unverified provider email as verified, MySQL serial IDs returning another request's record with specified Kysely and Drizzle adapters, and revoked sessions remaining valid with secondary storage or cookie cache. Other findings affect Email OTP, admin permissions, organization invitations, Stripe billing associations, and passkey verification. Remediation varies: examples include requiring fresh email-change codes, assigning the `set-phone` permission only to authorized roles, auditing invitations and memberships affected by padded role names, and checking whether Stripe customer IDs are associated with multiple users.

The bulletin distinguishes the version lines in a way that matters operationally. Both 1.7.16 and 1.8.0-beta.5 contain the listed fixes, but the phone-number mitigation differs: the beta line also validates ownership when a pending number is verified, including numbers stored before the upgrade. Teams should therefore record which line they operate before treating remediation instructions as interchangeable. They should also check every installed `@better-auth/*` package rather than assuming an upgrade to the core dependency alone covers an enabled plugin.

Vercel says it created WAF rules and deployed them automatically to all projects hosted on Vercel at no cost; no configuration change or redeploy is required for that layer. Its bulletin explicitly warns not to rely on WAF protection for full mitigation. Teams should upgrade `better-auth` and every `@better-auth/*` package they use to 1.7.16, or 1.8.0-beta.5 on the beta line, then read the advisory for each plugin they use because some fixes require configuration or cleanup.

## What the archive adds
This is a new security event, not a restatement of the earlier PHP advisory. In [our PHP2Shell note](https://newruntime.com/posts/php2shell-security-advisory-two-critical-rce-flaws-in-1be379/), Vercel also reported deploying WAF protections before disclosure while warning that patching remained essential. The shared point is the boundary: platform-level filtering can reduce exposure, but it does not replace fixing vulnerable application dependencies.

## Trend signal
This is a weak fit for [agent security moves to runtime boundaries](https://newruntime.com/patterns/agent-security-moves-to-runtime-boundaries/): the bulletin illustrates that security depends on controls outside a prompt, including patched dependencies, WAF rules, secrets, and authorization configuration. It is an authentication-library incident, however, and does not establish a trend specific to AI agents or runtime design.

## Why now
The coordinated release is available now, and Vercel describes protections already deployed to its hosted projects. The timing makes the upgrade and advisory-specific remediation immediate for teams that use affected Better Auth packages; the source does not provide a separate disclosure timeline.

## Why it matters
For teams building AI products, authentication is part of the system boundary around users, agents, and connected services. A bypass, exposed secret, stale session, or incorrect billing association can undermine controls even if model behavior is well specified. This release also shows why security response cannot stop at deploying a platform rule: some issues require rotating credentials, removing improperly verified data, correcting role assignments, or auditing persisted records. Teams should inventory the Better Auth core and plugins they actually use, upgrade them, and map each relevant advisory to its post-upgrade actions. A blanket “WAF is on” status is not evidence that an application is remediated.

## Limits and uncertainty
Vercel's bulletin summarizes the release and selected remediation details, but the supplied material does not establish how many applications are affected, whether any vulnerability was exploited, or the severity and affected-version range of every advisory. Applicability depends on package versions, plugins, configuration, and whether specific endpoints or features were enabled. The WAF statement applies to projects hosted on Vercel; it does not establish protection for other hosting environments. Teams need to consult the individual advisories for their dependencies and deployment conditions rather than infer exposure from the summary alone.

## Reader takeaway
Upgrade Better Auth and the plugins you use to the patched line, then follow the advisory-specific steps. Vercel's automatically applied WAF rules are a useful extra layer for its hosted projects, not a substitute for patching, secret rotation, or cleanup where required.

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Agent Security](https://newruntime.com/topics/agent-security.md): Explore the agent-security topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Sources](https://newruntime.com/sources/): See the original sources this archive cites.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)