{
  "affected": [
    {
      "ranges": [
        {
          "database_specific": {
            "cpe": "cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:*",
            "extracted_events": [
              {
                "introduced": "12.2.0"
              },
              {
                "fixed": "15.5.16"
              },
              {
                "introduced": "16.0.0"
              },
              {
                "fixed": "16.2.5"
              }
            ],
            "source": "CPE_RANGE"
          },
          "events": [
            {
              "introduced": "632feb6b73f68ab48004634909fe1be237db0e43"
            },
            {
              "fixed": "ad6fd4e50e5aba20b60d283c42b89273a3167ccd"
            },
            {
              "introduced": "950609f96f694c5475d18cd2d72a0052ca04d4b9"
            },
            {
              "fixed": "766148f9cd48c0e218acafcd0f15defc14871bf4"
            }
          ],
          "repo": "https://github.com/vercel/next.js",
          "type": "GIT"
        }
      ]
    }
  ],
  "aliases": [
    "GHSA-3g8h-86w9-wvmq"
  ],
  "database_specific": {
    "cna_assigner": "GitHub_M",
    "cwe_ids": [
      "CWE-349"
    ],
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/44xxx/CVE-2026-44572.json"
  },
  "details": "Next.js is a React framework for building full-stack web applications. From 12.2.0 to before 15.5.16 and 16.2.5, an external client could send a x-nextjs-data header on a normal request to a path handled by middleware that returns a redirect. When that happened, the middleware/proxy could treat the request as a data request and replace the standard Location redirect header with the internal x-nextjs-redirect header. Browsers do not follow x-nextjs-redirect, so the response became an unusable redirect for normal clients. If the application was deployed behind a CDN or reverse proxy that caches 3xx responses without varying on this header, a single attacker request could poison the cached redirect response for the affected path. Subsequent visitors could then receive a cached redirect response without a Location header, causing a denial of service for that redirect path until the cache entry expired or was purged. This vulnerability is fixed in 15.5.16 and 16.2.5.",
  "id": "CVE-2026-44572",
  "modified": "2026-07-15T01:49:12.810067494Z",
  "published": "2026-05-13T15:57:15.750Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/44xxx/CVE-2026-44572.json"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/vercel/next.js/security/advisories/GHSA-3g8h-86w9-wvmq"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-44572"
    }
  ],
  "schema_version": "1.8.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Next.js: Middleware / Proxy redirects can be cache-poisoned"
}