Vulnerabilities in pkg:npm/next
PACKAGECVE-2026-94544 is a MODERATE (CVSS 4.2) pending `use cache` fill can vulnerability (CWE-524: Use of Cache Containing Sensitive Information) affecting Next libraries in the npm ecosystem. The issue involves pending `use cache` fill can leak draft mode content into regular responses and persisted pages. Remediation is available by upgrading affected packages to version 16.3.8.
pkg:npm/next
Vulnerability advisories affecting package pkg:npm/next. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-3w37-wq28-93x7 | CVE-2026-94544 | MODERATE | Next.js: Pending `use cache` fill can leak Draft Mode content into regular responses and persisted pages |
| GHSA-4jqv-mc3x-m676 | CVE-2026-94543 | MODERATE | Next.js has cache poisoning of SSG and ISR pages in self-hosted applications |
| GHSA-39w2-rjm5-chcv | CVE-2026-94486 | LOW | Next.js has information disclosure in development server's Model Context Protocol endpoint |
| GHSA-f87g-xv8r-7p7x | CVE-2026-94485 | MODERATE | Next.js has information disclosure in App Router metadata image routes via dynamicParams bypass |
| GHSA-mcj8-r9mp-w47p | CVE-2026-94484 | MODERATE | Next.js has cache poisoning in SSG/ISR rendering that leads to cross-user content substitution and persistent denial of service |
| GHSA-cjq9-62q9-8jv4 | CVE-2026-94483 | HIGH | Next.js has Server-Side Request Forgery in Image Optimization |
| GHSA-vcvr-r3jv-pc5j | - | CRITICAL | Next.js: Remote Code Execution in next/og ImageResponse |
| GHSA-2xp9-vwfh-vxw4 | - | CRITICAL | Next.js: Unauthenticated Remote Code Execution in Image Optimization API when AVIF files are used |
| GHSA-p293-qw3h-jr36 | CVE-2026-75604 | CRITICAL | Next.js: Unauthenticated Remote Code Execution on windows-hosted servers |
| GHSA-89xv-2m56-2m9x | CVE-2026-64649 | HIGH | Next.js: Server-Side Request Forgery in Server Actions on custom servers |
| GHSA-68g3-v927-f742 | CVE-2026-64648 | MODERATE | Next.js: Cache confusion of response bodies for requests with bodies |
| GHSA-4633-3j49-mh5q | CVE-2026-64647 | MODERATE | Next.js: Cache confusion of response bodies for requests with bodies containing invalid UTF-8 byte sequences |
| GHSA-4c39-4ccg-62r3 | CVE-2026-64646 | MODERATE | Next.js: Unbounded Server Action payload in Edge runtime |
| GHSA-p9j2-gv94-2wf4 | CVE-2026-64645 | HIGH | Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostname |
| GHSA-q8wf-6r8g-63ch | CVE-2026-64644 | MODERATE | Next.js: Denial of Service in the Image Optimization API using SVGs |
| GHSA-955p-x3mx-jcvp | CVE-2026-64643 | MODERATE | Next.js: Unauthenticated disclosure of internal Server Function endpoints |
| GHSA-6gpp-xcg3-4w24 | CVE-2026-64642 | HIGH | Next.js: Middleware / Proxy bypass in App Router applications using Turbopack and single locale |
| GHSA-m99w-x7hq-7vfj | CVE-2026-64641 | HIGH | Next.js: Denial of Service in App Router using Server Actions |
| GHSA-26hh-7cqf-hhc6 | CVE-2026-45109 | HIGH | Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes - Incomplete Fix Follow-Up |
| GHSA-ffhc-5mcf-pf4q | CVE-2026-44581 | MODERATE | Next.js vulnerable to cross-site scripting in App Router applications using CSP nonces |
| GHSA-vfv6-92ff-j949 | CVE-2026-44582 | LOW | Next.js vulnerable to cache poisoning via collisions in React Server Component cache-busting |
| GHSA-gx5p-jg67-6x7h | CVE-2026-44580 | MODERATE | Next.js has cross-site scripting in beforeInteractive scripts with untrusted input |
| GHSA-mg66-mrh9-m8jx | CVE-2026-44579 | HIGH | Next.js vulnerable to Denial of Service via connection exhaustion in applications using Cache Components |
| GHSA-c4j6-fc7j-m34r | CVE-2026-44578 | HIGH | Next.js vulnerable to server-side request forgery in applications using WebSocket upgrades |
| GHSA-h64f-5h5j-jqjh | CVE-2026-44577 | MODERATE | Next.js has a Denial of Service in the Image Optimization API |
| GHSA-wfc6-r584-vfw7 | CVE-2026-44576 | MODERATE | Next.js vulnerable to cache poisoning in React Server Component responses |
| GHSA-267c-6grr-h53f | CVE-2026-44575 | HIGH | Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes |
| GHSA-492v-c6pp-mqqv | CVE-2026-44574 | HIGH | Next.js has a Middleware / Proxy bypass through dynamic route parameter injection |
| GHSA-36qx-fr4f-26g5 | CVE-2026-44573 | HIGH | Next.js has a Middleware / Proxy bypass in Pages Router applications using i18n |
| GHSA-3g8h-86w9-wvmq | CVE-2026-44572 | LOW | Next.js's Middleware / Proxy redirects can be cache-poisoned |
| GHSA-8h8q-6873-q5fj | - | HIGH | Next.js Vulnerable to Denial of Service with Server Components |
| GHSA-q4gf-8mx6-v5v3 | - | HIGH | Next.js has a Denial of Service with Server Components |
| GHSA-5f7q-jpqc-wp7h | CVE-2025-59472 | MODERATE | Next.js has Unbounded Memory Consumption via PPR Resume Endpoint |
| GHSA-jcc7-9wpm-mj36 | CVE-2026-27977 | LOW | Next.js: null origin can bypass dev HMR websocket CSRF checks |
| GHSA-3x4c-7xq6-9pq8 | CVE-2026-27980 | MODERATE | Next.js: Unbounded next/image disk cache growth can exhaust storage |
| GHSA-h27x-g6w4-24gq | CVE-2026-27979 | MODERATE | Next.js: Unbounded postponed resume buffering can lead to DoS |
| GHSA-mq59-m269-xvcx | CVE-2026-27978 | MODERATE | Next.js: null origin can bypass Server Actions CSRF checks |
| GHSA-ggv3-7p47-pfv8 | CVE-2026-29057 | MODERATE | Next.js: HTTP request smuggling in rewrites |
| GHSA-f82v-jwr5-mffw | CVE-2025-29927 | CRITICAL | Authorization Bypass in Next.js Middleware |
| GHSA-h25m-26qc-wcjf | - | HIGH | Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components |
| GHSA-9g9p-9gw9-jx7f | CVE-2025-59471 | MODERATE | Next.js self-hosted applications vulnerable to DoS via Image Optimizer remotePatterns configuration |
| GHSA-5j59-xgg2-r9c4 | - | HIGH | Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up |
| GHSA-w37m-7fhw-fmv9 | - | MODERATE | Next Server Actions Source Code Exposure |
| GHSA-mwv6-3258-q52c | - | HIGH | Next Vulnerable to Denial of Service with Server Components |
| GHSA-9qr9-h5gf-34mp | - | CRITICAL | Next.js is vulnerable to RCE in React flight protocol |
| GHSA-223j-4rm8-mrmf | CVE-2025-30218 | LOW | Next.js may leak x-middleware-subrequest-id to external hosts |
| GHSA-fq77-7p7r-83rj | CVE-2020-5284 | MODERATE | Directory Traversal in Next.js |
| GHSA-qpjv-v59x-3qc4 | CVE-2025-32421 | LOW | Next.js Race Condition to Cache Poisoning |
| GHSA-4342-x723-ch2f | CVE-2025-57822 | MODERATE | Next.js Improper Middleware Redirect Handling Leads to SSRF |
| GHSA-xv57-4mr9-wg8v | CVE-2025-55173 | MODERATE | Next.js Content Injection Vulnerability for Image Optimization |
| GHSA-fr5h-rqp8-mj6g | CVE-2024-34351 | HIGH | Next.js Server-Side Request Forgery in Server Actions |
| GHSA-7gfc-8cq8-jh5f | CVE-2024-51479 | HIGH | Next.js authorization bypass vulnerability |
| GHSA-g5qg-72qw-gw5v | CVE-2025-57752 | MODERATE | Next.js Affected by Cache Key Confusion for Image Optimization API Routes |
| GHSA-67rr-84xm-4c7r | CVE-2025-49826 | HIGH | Next.JS vulnerability can lead to DoS via cache poisoning |
| GHSA-r2fc-ccr8-96c4 | CVE-2025-49005 | LOW | Next.js has a Cache poisoning vulnerability due to omission of the Vary header |
| GHSA-3h52-269p-cp9r | CVE-2025-48068 | LOW | Information exposure in Next.js dev server due to lack of origin verification |
| GHSA-7m27-7ghc-44w9 | CVE-2024-56332 | MODERATE | Next.js Allows a Denial of Service (DoS) with Server Actions |
| GHSA-g77x-44xx-532m | CVE-2024-47831 | MODERATE | Denial of Service condition in Next.js image optimization |
| GHSA-fq54-2j52-jc42 | CVE-2024-39693 | HIGH | Next.js Denial of Service (DoS) condition |
| GHSA-gp8f-8m3g-qvj9 | CVE-2024-46982 | HIGH | Next.js Cache Poisoning |
| GHSA-77r5-gw3j-2mpf | CVE-2024-34350 | HIGH | Next.js Vulnerable to HTTP Request Smuggling |
| GHSA-3f5c-4qxj-vmpf | CVE-2017-16877 | HIGH | Next.js Directory Traversal Vulnerability |
| GHSA-25mp-g6fv-mqxx | CVE-2021-43803 | HIGH | Unexpected server crash in Next.js. |
| GHSA-c59h-r6p8-q9wc | CVE-2023-46298 | LOW | Next.js missing cache-control header may lead to CDN caching empty reply |
| GHSA-wff4-fpwg-qqv3 | CVE-2022-36046 | MODERATE | Unexpected server crash in Next.js |
| GHSA-vxf5-wxwp-m7g9 | CVE-2021-37699 | MODERATE | Open Redirect in Next.js |
| GHSA-m34x-wgrh-g897 | CVE-2018-6184 | HIGH | Directory traversal vulnerability in Next.js |
| GHSA-5vj8-3v2h-h38v | - | HIGH | Remote Code Execution in next |
| GHSA-qw96-mm2g-c8m7 | CVE-2018-18282 | MODERATE | Next.js has cross site scripting (XSS) vulnerability via the 404 or 500 /_error page |
| GHSA-fmvm-x8mv-47mj | CVE-2022-23646 | MODERATE | Improper CSP in Image Optimization API for Next.js versions between 10.0.0 and 12.1.0 |
| GHSA-wr66-vrwm-5g5x | CVE-2022-21721 | MODERATE | Denial of Service Vulnerability in next.js |
| GHSA-x56p-c8cg-q435 | CVE-2020-15242 | MODERATE | Open Redirect in Next.js versions |
| GHSA-9gr3-7897-pp7m | CVE-2021-39178 | HIGH | XSS in Image Optimization API for Next.js |
CVE-2026-94544 at a Glance
Security Impact
CVSS: 4.2
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N).
How to Fix CVE-2026-94544
To remediate this vulnerability, upgrade all affected Next dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install next@16.3.8
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls next
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-94544, inspect your project dependencies using npm:
npm ls next
Analyze the terminal output to locate any version of Next in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 16.3.8), your application is affected.
Note: The npm ls next command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-524: Use of Cache Containing Sensitive Information, where the code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere. In Next, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-94544 Affected Next Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
next
|
npm |
≥ 16.3.0
< 16.3.8
|
16.3.8
|
References
Frequently Asked Questions
What is CVE-2026-94544?
Which Next versions are affected?
What version fixes CVE-2026-94544?
Is next affected?
What is the CVSS score of CVE-2026-94544?
What CWE is associated with CVE-2026-94544?
How can I check npm dependencies for CVE-2026-94544?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-3w37-wq28-93x7",
"modified" : "2026-10-07T20:32:13Z",
"published" : "2026-10-07T20:32:13Z",
"aliases" : [ "CVE-2026-94544" ],
"summary" : "Next.js: Pending `use cache` fill can leak Draft Mode content into regular responses and persisted pages",
"details" : "Pending `use cache` fills are shared across requests for the same key without distinguishing Draft Mode requests from regular requests. When two such requests overlap, the second request receives the first request's fill:\n\n- A regular request that overlaps an editor's Draft Mode request receives unpublished content, without any authentication.\n- A Draft Mode request that overlaps a regular request receives published content instead of the draft.\n\nIf the overlapping regular request prerenders a page — for example an on-demand prerender of a route that was not prerendered at build time — the unpublished content can be persisted into the generated page and served to all later visitors of that route until the page is revalidated. Since cached functions can be shared across routes, the poisoned page does not need to be the page the editor is previewing.\n\nSites are affected if they enable Cache Components (or `experimental.useCache`) and serve Draft Mode previews whose cached functions return draft-dependent content.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N"
}, {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "next"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "16.3.0"
}, {
"fixed" : "16.3.8"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/vercel/next.js/security/advisories/GHSA-3w37-wq28-93x7"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-94544"
}, {
"type" : "WEB",
"url" : "https://github.com/vercel/next.js/commit/bd9214f9a32854a011bf5fe58e481dffe1bbf598"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/vercel/next.js"
}, {
"type" : "WEB",
"url" : "https://github.com/vercel/next.js/releases/tag/v16.3.8"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-524" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-10-07T20:32:13Z",
"nvd_published_at" : "2026-10-02T16:16:52Z"
}
}