{"id":"GHSA-h64f-5h5j-jqjh","revision":"a63b3c7a043f464ab65a6bd312961d39","records":[{"revision":"a63b3c7a043f464ab65a6bd312961d39","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"GHSA-h64f-5h5j-jqjh","aliases":["CVE-2026-44577"],"title":"Next.js has a Denial of Service in the Image Optimization API","description":"### Impact\n\nWhen self-hosting Next.js with the default image loader, the Image Optimization API fetches local images entirely into memory without enforcing a maximum size limit. An attacker could cause out-of-memory conditions by requesting large local assets from the `/_next/image` endpoint that match the `images.localPatterns` configuration (by default, all patterns are allowed).\n\n- If you are using `images.localPatterns`, only the patterns in that array are impacted.\n- If you are using `images.unoptimized: true`, you are NOT impacted.\n- If you are using `images.loader: 'custom'`, you are NOT impacted.\n- If you are using Vercel, you are NOT impacted.\n\n### Fix\n\nWe now apply response size limits consistently to internal image fetches, not just external ones, and fail oversized responses before they can exhaust process memory.\n\nThis can be adjusted using the `images.maximumResponseBody` configuration.\n\n### Workarounds\n\nIf you cannot upgrade immediately, avoid routing large local assets through `/_next/image`, disable image optimization for large or untrusted local files, or block image optimization access to those assets at the edge.\n\nYou can disable using the `images.localPatterns: []` configuration. This will still allow fetching remote images (which is not impacted).","state":0,"publishedAt":"2026-05-11T15:56:05+00:00","modifiedAt":"2026-09-10T03:50:47.1515456+00:00","affected":[{"ecosystem":"npm","name":"next","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"10.0.0"},{"kind":"fixed","version":"15.5.16"}]}],"versions":[],"rawVersionEvidence":null},{"ecosystem":"npm","name":"next","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"16.0.0"},{"kind":"fixed","version":"16.2.5"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V3","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"MODERATE"}],"references":["https://github.com/vercel/next.js/security/advisories/GHSA-h64f-5h5j-jqjh","https://nvd.nist.gov/vuln/detail/CVE-2026-44577","https://github.com/vercel/next.js","https://github.com/vercel/next.js/releases/tag/v15.5.16","https://github.com/vercel/next.js/releases/tag/v16.2.5"],"sourceUrl":"https://github.com/advisories/GHSA-h64f-5h5j-jqjh","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-h64f-5h5j-jqjh","identifiers":["GHSA-h64f-5h5j-jqjh","CVE-2026-44577"]},"retained":false,"historicalAffected":[]}],"coverage":[]}