CVE-2025-29927: Next.js Middleware Authorization Bypass
- Vendor
- Vercel
CVE-2025-29927 is an authorization bypass vulnerability in Next.js that allows remote attackers to skip middleware processing by spoofing the internal x-middleware-subrequest HTTP header. Applications that enforce authentication or authorization exclusively in middleware can consequently forward attacker requests to protected endpoints without performing those checks. Affected releases begin at 11.1.4, with fixes available in 12.3.5, 13.5.9, 14.2.25, and 15.2.3 for their respective release lines.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can expose protected resources and functionality to unauthorized users, compromising data confidentiality and potentially integrity where protected endpoints support state-changing actions. Other middleware-dependent protections may also be bypassed. Depending on application behavior, additional effects can include Content Security Policy bypass or denial of service through cache poisoning. Impact is constrained by any independent authentication and authorization checks enforced beyond middleware.
Mitigation
If you can’t patch tonight, do this now.
Prevent external user requests containing the x-middleware-subrequest header from reaching the Next.js application, enforcing the restriction at a trusted reverse proxy, gateway, or WAF across all externally reachable ingress paths. Vercel-hosted deployments were automatically protected against this vulnerability; Netlify-hosted deployments are also identified as protected.
Remediation
Patch, then assume compromise.
Upgrade Next.js to a patched release: 12.3.5 or later in the 12.x line, 13.5.9 or later in 13.x, 14.2.25 or later in 14.x, or 15.2.3 or later in 15.x. Prefer a currently supported release containing the fix. No fixed 11.x release is identified; migrate to a patched release line or apply the header-blocking workaround until migration is complete.
Exploits
74 exploits validated by Mallory's analysis. Hidden: 68 rejected by Mallory's analysis as not a working exploit; 5 not yet analyzed, such as Exploit-DB entries. Showing the 25 most capable, earliest first.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2025-29927 exploited in the wild?
- Yes. As of Nov 15, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2025-29927?
- Yes. Mallory tracks 74 public exploits or proofs of concept for CVE-2025-29927, the earliest disclosed Mar 23, 2025.
- Is there a patch for CVE-2025-29927?
- Upgrade Next.js to a patched release: 12.3.5 or later in the 12.x line, 13.5.9 or later in 13.x, 14.2.25 or later in 14.x, or 15.2.3 or later in 15.x. Prefer a currently supported release containing the fix.
- What products are affected by CVE-2025-29927?
- Vercel Next.Js.
- How severe is CVE-2025-29927?
- CVE-2025-29927 has a CVSS v3.1 score of 9.1 (Critical) and an EPSS score of 99.2% (100th percentile) as of Nov 15, 2026.
Recent activity
111 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.