Skip to main content
Mallory
← Back to News
internet-facing-service-vulnerabilityproof-of-concept-releasewidely-deployed-product-advisorycloud-service-vulnerability

Next.js patches SSRF and authorization bypass flaws in self-hosted apps

Vulnerability Disclosure · 8 sources · Updated 5mo ago · First seen May 15, 2026

Vercel issued a coordinated Next.js security release covering 13 advisories, including a high-severity server-side request forgery flaw tracked as CVE-2026-44578 / GHSA-c4j6-fc7j-m34r. The bug affects self-hosted applications using the built-in Node.js server, where crafted WebSocket upgrade requests can be abused to proxy traffic to arbitrary internal or external destinations. That exposure can let attackers reach cloud metadata endpoints, internal admin interfaces, and other internal services, potentially stealing cloud credentials, API keys, and deployment secrets. Vercel-hosted deployments were reported as unaffected because they do not use the vulnerable WebSocket routing path.

The release also fixed an App Router authorization bypass, GHSA-267c-6grr-h53f, in which specially crafted .rsc and segment-prefetch URLs could evade middleware or proxy-based access controls and expose protected content. A public GitHub repository has since collected proof-of-concept material for 12 issues fixed in next 16.2.5, including SSRF, middleware bypass, cache poisoning, XSS, and denial-of-service bugs, increasing the urgency for defenders to patch. Vercel said patching is the only complete mitigation and advised upgrading to Next.js 15.5.18 or 16.2.6, with immediate interim steps including blocking unnecessary WebSocket upgrades, restricting origin-server egress to metadata and internal networks, and enforcing authorization checks in route or page logic rather than relying solely on middleware.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

8 events · May 6, 2026 – May 15, 2026
  1. May 15, 20266mo ago

    Reporting highlights SSRF risk to cloud credentials and internal services

    Public reporting summarized CVE-2026-44578 as a high-severity SSRF vulnerability that could expose cloud metadata, API keys, deployment secrets, and internal admin interfaces in self-hosted Next.js deployments. The coverage reiterated fixed versions and recommended mitigations such as blocking unnecessary WebSocket upgrades and restricting origin egress.

  2. May 8, 20266mo ago

    Public PoC repository appears for Next.js 16.2.5-fixed vulnerabilities

    A GitHub repository was published collecting reverse-engineered proof-of-concept material for 12 security issues fixed in Next.js 16.2.5. The repository includes exploit scripts, patch diffs, vulnerable code excerpts, and reproduction material for defensive research and regression testing.

  3. May 7, 20267mo ago

    Next.js releases fixes for May 2026 security advisories

    As part of its May 2026 security release, Next.js shipped coordinated fixes for 13 advisories covering issues including denial of service, authorization bypasses, SSRF, cache poisoning, and XSS. The release notes direct users to upgrade Next.js and related React packages, emphasizing that patching is the only complete mitigation.

  4. May 7, 20267mo ago

    Next.js issues follow-up advisory for incomplete App Router bypass fix

    Vercel published advisory GHSA-26hh-7cqf-hhc6 describing an incomplete-fix follow-up for middleware or proxy bypass in App Router applications via segment-prefetch routes. The advisory indicates the originally disclosed bypass issue required additional remediation beyond the initial fix.

    Middleware / Proxy bypass in App Router applications via segment-prefetch routes - Incomplete Fix Follow-Up · Advisory · vercel/next.js · GitHub
  5. May 6, 20267mo ago

    Next.js discloses Pages Router i18n middleware bypass

    Vercel published advisory GHSA-36qx-fr4f-26g5 for an authorization bypass affecting Pages Router applications with i18n enabled that rely on middleware or proxy-based access controls. Locale-less /_next/data/<buildId>/<page>.json requests could bypass middleware and expose protected server-side rendered JSON, with fixes released in 15.5.16 and 16.2.5.

    Middleware / Proxy bypass in Pages Router applications using i18n · Advisory · vercel/next.js · GitHub
  6. May 6, 20267mo ago

    Next.js discloses dynamic route parameter middleware bypass

    Vercel published advisory GHSA-492v-c6pp-mqqv for an authorization bypass affecting Next.js applications that use middleware to protect dynamic routes. Specially crafted query parameters could alter the dynamic route value processed by the page while leaving the visible path unchanged, and the issue was fixed in versions 15.5.16 and 16.2.5.

    Middleware / Proxy bypass through dynamic route parameter injection · Advisory · vercel/next.js · GitHub
  7. May 6, 20267mo ago

    Next.js discloses App Router middleware bypass vulnerability

    Vercel published advisory GHSA-267c-6grr-h53f covering an authorization bypass in App Router applications that rely on middleware or proxy-based checks. Crafted .rsc and segment-prefetch URLs could bypass intended middleware protections in affected 15.x and 16.x releases.

  8. May 6, 20267mo ago

    Next.js discloses SSRF flaw in WebSocket upgrade handling

    Vercel published advisory GHSA-c4j6-fc7j-m34r for CVE-2026-44578, describing an SSRF issue in self-hosted Next.js applications using the built-in Node.js server. The flaw affects versions 13.4.13 through before 15.5.16 and 16.0.0 through before 16.2.5, while Vercel-hosted deployments are stated to be unaffected.

Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Source coverage

Sources

8 references tracked. Mallory keeps watching after this page renders.

Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.