AI provider API key leaked? Rotate it, cap spend, check usage
Replace and revoke the key, set a spend cap, and check usage. Steps for OpenAI, Anthropic, the Gemini API and Vertex AI, from each provider's docs.
next versionThe September 2026 Next.js security release fixes an Image Optimization SSRF and several cache-poisoning issues. Upgrade next on your line and redeploy.

This is a version check only. If your app uses Next.js 15.x or 16.x, upgrade to a patched release and redeploy.
npm install next@15.5.27 # Maintenance LTS (15.5.x)
npm install next@16.3.8 # Active LTS (16.3.x)
Those install lines are from the official Next.js security blog (September 2026 Security Release). Matching GitHub releases: v16.3.8, v15.5.27.
After upgrading, redeploy. If you use images.remotePatterns, also audit allow-listed remote hosts (see below).
From the September 2026 Security Release and the linked advisories:
| Issue | Severity | Advisory | Notes |
|---|---|---|---|
| SSRF in Image Optimization | High | GHSA-cjq9-62q9-8jv4 / CVE-2026-94483 | Attacker-controlled, allow-listed remote URL can lead to SSRF (e.g. private IPs) during Image Optimization. If no images.remotePatterns are configured, your app is not affected by this one. |
| Cache poisoning (SSG/ISR, catch-all) | Medium | GHSA-mcj8-r9mp-w47p / CVE-2026-94484 | Shared response cache can be poisoned by a crafted request. |
| Cache poisoning (self-hosted Pages Router SSG/ISR) | Medium | GHSA-4jqv-mc3x-m676 / CVE-2026-94543 | Wrong content served until revalidation. Blog notes apps on Vercel are not affected by this specific advisory. |
Draft Mode / use cache leak | Medium | GHSA-3w37-wq28-93x7 / CVE-2026-94544 | Overlapping Draft Mode and regular requests can leak unpublished content. |
Metadata image dynamicParams bypass | Medium | GHSA-f87g-xv8r-7p7x / CVE-2026-94485 | Webpack App Router metadata image routes. Turbopack builds not affected per the blog. |
Nested use cache root-param leak | Medium | GHSA-h694-7cp9-m8p3 | Cache Components. |
| Dev-server MCP endpoint info disclosure | Low | GHSA-39w2-rjm5-chcv / CVE-2026-94486 | Only next dev; production does not serve this endpoint. |
We are not ranking hosts or builders. If next is in your lockfile below the patched versions, upgrade.
next version pinned “because the app still works.”Check package.json and the lockfile for the "next" dependency version.
If it is on the 15.x line and below 15.5.27, or on the 16.x line and below 16.3.8,
propose upgrading to next@15.5.27 or next@16.3.8 respectively (stay on the same major line).
Show the diff and any peer-dependency notes first. Do not upgrade unrelated packages.
Wait for my OK before applying. After upgrade, remind me to audit images.remotePatterns
if we use remote images.
npm ls next (or your package manager’s equivalent) shows 15.5.27 or 16.3.8 (or newer on that line).images.remotePatterns for hosts you trust (Next.js images docs, linked from GHSA-cjq9-62q9-8jv4).Pre-launch checklist · Own-cloud security guide · Secret key in frontend bundle
Were you on 15.x or 16.x when you checked? Tell us which install line you used. We’ll keep the version table current when the next security release lands.
This guide is educational and based on the vendor's public docs as of the review date. Platforms change: check the linked sources. Not a security audit. Disclaimer.
From BuiltSafely · builtsafely.com · https://builtsafely.com/fixes/nextjs-security-release/
The BuiltSafely weekly
Platform changes that affect the security of AI-built apps, checked against official docs. Free. Unsubscribe any time.