Skip to main content

How to fix: X-Vercel-Id reveals deployment platform

The X-Vercel-Id header is present and reveals the application is hosted on Vercel.

Why it matters

Revealing the deployment platform enables targeted attacks specific to Vercel's architecture, including serverless function cold-start timing attacks, deployment URL enumeration, or platform-specific configuration issues.

Vercel headers can be suppressed via custom Next.js middleware.

How to fix it

  1. 1In Next.js middleware, you can strip headers before they are forwarded

Code examples

Next.js middleware: strip Vercel headers

TypeScript
import { NextResponse, type NextRequest } from "next/server";

export function middleware(req: NextRequest) {
  const res = NextResponse.next();
  res.headers.delete("x-vercel-id");
  res.headers.delete("x-vercel-cache");
  return res;
}

References

Detected automatically by VulnRadar. The check id is x-vercel-id, stable across every scan so you can filter or diff on it.

See every headers check

Questions

How severe is X-Vercel-Id reveals deployment platform?
VulnRadar rates this info severity in the headers category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id x-vercel-id, which stays the same between runs so you can filter, diff, or gate CI on it.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for x-vercel-id reveals deployment platform

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

X-Vercel-Id reveals deployment platform fix | VulnRadar