Works with the AI Agents you already use
Next.js Security Patch Nov 2026: Is My App Affected? Check, Upgrade to 16.4.5 / 15.5.29, Prove It
Per-advisory exposure verdicts with file evidence for the 7 Next.js November 2026 security fixes, the minimal upgrade, and a verified report.
$1
Next.js Security Patch Nov 2026: Is My App Affected? Check, Upgrade to 16.4.5 / 15.5.29, Prove It
Example session with this skill installed
Our monorepo has apps/web (Next.js 16) and apps/admin (Next.js 15), deployed in Docker. Are we affected by the November Next.js security release? Patch it if so.
- Read your context and instructions
- Compiled the next js security
- Generated the document
Next.js November 2026 Security Release: Exposure Report
Repository: acme (test monorepo) · Checked: 11 Nov 2026 · Facts as of: 11 Nov 2026
Summary
Both apps were vulnerable: web was exposed to 2 issues (2 more possible), admin to none in practice. Both lockfile entries now resolve to fixed versions.
Installations
| App | Before | After | Status |
|---|---|---|---|
| apps/web | 16.4.2 | 16.4.6 | PATCHED |
| apps/admin | 15.3.9 | 15.5.29 | PATCHED |
Exposure by advisory (before upgrade, apps/web on 16.4.2)
| # | Advisory | Verdict | Evidence |
|---|---|---|---|
| 1 | GHSA-mfr8-8qww-v76h | EXPOSED (race-dependent) | app/lib/data.ts:8 unstable_cache(getPlans, ...) wraps a 'use cache' fn that reads next/root-params (line 2); next.config.ts:1 cacheComponents: true |
| 2 | GHSA-vc7v-qv4w-wrv8 | NOT EXPOSED | getPlans is not nested inside another cached function |
| 3 | GHSA-rhh4-g77r-r9qj | NOT EXPOSED | no Uint8Array/Blob arguments in cached functions |
| 4 | Shared shell poisoning | POSSIBLY EXPOSED | self-hosted (Dockerfile, output 'standalone'); Partial Prefetching unset; route shape not confirmed |
| 5 | GHSA-pc58-hwjq-p385 | NOT EXPOSED | no return fetch( in apps/web |
| 6 | GHSA-f3mh-rxg3-f5g2 | EXPOSED | app/api/session/route.ts:2 runtime = 'edge', :5 res.cookies.set('session', ...) |
| 7 | GHSA-7qx7-33qx-rqx2 | POSSIBLY EXPOSED | page.tsx:1 next/image; remotePatterns cdn.example.com; self-hosted. Depends on who can upload to the CDN |
apps/admin (15.3.9): only issues 6 and 7 apply; no Edge routes and no next/image, so NOT EXPOSED. pages/api/proxy.ts:1 returns fetch(), but issue 5 does not affect 15.x.
Verification
| Check | Command | Result |
|---|---|---|
| Re-scan | python3 scripts/scan_next_exposure.py . | next@16.4.6 PATCHED, next@15.5.29 PATCHED |
| Build and tests | npm run build / npm test | run in your project; record exit codes here |
Open items
- Issue 4: confirm whether any dynamic route has two un-prerendered deeper params with a blocking fallback.
- Issue 7: confirm whether users can upload files to cdn.example.com.
page.tsx
PDF · document
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
About this skill
On 3 November 2026 Next.js released fixes for seven security issues: four cache disclosure or poisoning bugs around use cache, unstable_cache and Cache Components, a response-injection bug behind pipelining proxies, a cookie leak in Edge routes, and an SVG filter bypass in Image Optimization. The fixed versions are 16.4.5 (Active LTS) and 15.5.29 (Maintenance LTS).
A scanner can tell you that next is outdated. It cannot tell you which of the seven issues your app is actually exposed to. This skill does that:
- Finds every copy of Next.js in the repo from the lockfile (npm, pnpm, Yarn, Bun), including nested workspaces in monorepos.
- Classifies each version: patched, vulnerable (and to which issues: 15.x is only hit by 2 of the 7), unsupported (14.x and older) or pre-release.
- Gives a verdict per advisory (EXPOSED / POSSIBLY EXPOSED / NOT EXPOSED / NOT APPLICABLE) backed by
path:lineevidence, using each advisory's real preconditions: Cache Components, root params, binary cache arguments, Edge routes setting cookies, self-hosted Image Optimization,return fetch()behind an HTTP/1.1 proxy. - Applies the smallest upgrade for each package manager, with overrides/resolutions handled, plus vendor-stated interim mitigations if you cannot upgrade today.
- Proves the result: lockfile check, build, tests and a re-scan, then a self-check list before the report is handed over.
Includes a read-only, standard-library Python scanner and a reference sheet of all seven advisories (IDs, affected ranges, preconditions, sources) checked on 11 November 2026 against nextjs.org and the GitHub advisories.
Output: NEXTJS-SECURITY-2026-11.md, a report you can attach to a ticket or security review.
Covers only the seven issues in the 3 November 2026 Next.js security release; it is not a general security audit. The scanner finds leads with pattern matching; verdicts need the agent to read the code. Hosting and reverse-proxy details often cannot be seen from the repo, so some verdicts will be POSSIBLY EXPOSED until you answer one question. The vendor has not said whether Vercel-hosted apps are affected, so the skill never treats Vercel hosting as proof of safety. Next.js 14 and older receive no fix and need a major upgrade, which this skill does not perform. Facts were checked on 11 November 2026; advisories can be edited later.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 6 days ago
Requires
Permissions
Allowed Hosts
File Scopes
The bundled scanner is read-only and uses only the Python standard library. Upgrades run through your own package manager.