Skip to content
Heist/ feed
Back to feed
High

Next.js DoS vulnerability via cache poisoning

Type: advisorySources: OSV

Next.js is a React framework for building full-stack web applications. From versions 15.0.4-canary.51 to before 15.1.8, a cache poisoning bug leading to a Denial of Service (DoS) condition was found in Next.js. This issue does not impact customers hosted on Vercel. Under certain conditions, this issue may allow a HTTP 204 response to be cached for static pages, leading to the 204 response being served to all users attempting to access the page. This issue has been addressed in version 15.1.8.

Products
Not specified
Affected versions
Not specified
Fixed versions
Not specified
CVEs
CVE-2025-49826
Confirmed fixed CVEs
Not specified
Updated in this feed
4 Nov 2026, 13:52 UTC · Revision 1

Source evidence

Next.js DoS vulnerability via cache poisoning

core-osv · Original source

Published 3 Jul 2025, 21:03 UTC

Next.js is a React framework for building full-stack web applications. From versions 15.0.4-canary.51 to before 15.1.8, a cache poisoning bug leading to a Denial of Service (DoS) condition was found in Next.js. This issue does not impact customers hosted on Vercel. Under certain conditions, this issue may allow a HTTP 204 response to be cached for static pages, leading to the 204 response being served to all users attempting to access the page. This issue has been addressed in version 15.1.8.

osv:CVE-2025-49826
Complete source record
{
  "id": "462730a05da049e00000f3bfa2ef96df57be4ae48fcd358c30369dc21c70512b",
  "url": "https://osv.dev/vulnerability/CVE-2025-49826",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "Next.js DoS vulnerability via cache poisoning",
    "summary": "Next.js is a React framework for building full-stack web applications. From versions 15.0.4-canary.51 to before 15.1.8, a cache poisoning bug leading to a Denial of Service (DoS) condition was found in Next.js. This issue does not impact customers hosted on Vercel. Under certain conditions, this issue may allow a HTTP 204 response to be cached for static pages, leading to the 204 response being served to all users attempting to access the page. This issue has been addressed in version 15.1.8.",
    "evidence": "osv:CVE-2025-49826",
    "products": [],
    "severity": "high",
    "structured": {
      "id": "CVE-2025-49826",
      "aliases": [
        "CVE-2025-49826",
        "GHSA-67rr-84xm-4c7r"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://github.com/vercel/next.js",
              "type": "GIT",
              "events": [
                {
                  "introduced": "3970d33e6d4bb055a8596c2b6f7ddbcaa5ca55dc"
                },
                {
                  "fixed": "ceaabaf5434dcfab31ba46b5ec2292f30e0f1b16"
                },
                {
                  "fixed": "a15b974ed707d63ad4da5b74c1441f5b7b120e93"
                }
              ],
              "database_specific": {
                "extracted_events": [
                  {
                    "range": [
                      {
                        "introduced": "15.0.4-canary.51"
                      },
                      {
                        "fixed": "15.1.8"
                      }
                    ],
                    "source": "AFFECTED_FIELD",
                    "strategy": "StringRangeExpression"
                  },
                  {
                    "range": [
                      {
                        "fixed": "a15b974ed707d63ad4da5b74c1441f5b7b120e93"
                      }
                    ],
                    "source": "REFERENCES_COMMIT"
                  },
                  {
                    "range": [
                      {
                        "fixed": "ceaabaf5434dcfab31ba46b5ec2292f30e0f1b16"
                      }
                    ],
                    "source": "REFERENCES_TAG",
                    "original_tag": "v15.1.8"
                  }
                ]
              }
            }
          ],
          "versions": [
            "15.0.4-canary51",
            "15.0.4-canary52",
            "v15.1.7",
            "v15.1.6",
            "v15.1.5",
            "v15.1.4",
            "v15.1.3",
            "v15.1.2",
            "v15.1.1",
            "v15.1.0",
            "v15.0.4-canary.52",
            "v15.0.4-canary.51"
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-49826.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:36.291438700Z",
      "provider": "osv",
      "references": [
        "https://github.com/vercel/next.js/releases/tag/v15.1.8",
        "https://vercel.com/changelog/cve-2025-49826",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/49xxx/CVE-2025-49826.json",
        "https://github.com/vercel/next.js/security/advisories/GHSA-67rr-84xm-4c7r",
        "https://nvd.nist.gov/vuln/detail/CVE-2025-49826",
        "https://github.com/vercel/next.js/commit/a15b974ed707d63ad4da5b74c1441f5b7b120e93"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-444"
        ],
        "cna_assigner": "GitHub_M",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/49xxx/CVE-2025-49826.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2025-49826",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 503316,
  "published_at": "2025-07-03T21:03:24.346+00:00"
}