AI & Agent Dev Bug Sandbox Back to Radar

App Router Boundary (Loading/Template/Error) Chunk <Script> Is Emitted Without The CSP Nonce

When using a nonce-based strict CSP, Next.js App Router fails to add the nonce attribute to the parser-inserted <script> tag for Suspense boundary chunks (loading.tsx, template.tsx, error.tsx). This causes the script to be blocked by 'strict-dynamic' on full page loads, leading to console violations and potentially broken client-side functionality.

highConfidence 92%Next.js Affected V16.2.11 Affected V16.3.3 Affected V16.4.0-Canary.10

Origin Analysis

In `packages/next/src/server/app-render/create-component-styles-and-scripts.ts` (compiled to `create-component-styles-and-scripts.js`), the script element for boundary chunks is created without passing `nonce: ctx.nonce`, while the analogous code in `get-layer-assets.ts` does include the nonce. As a result, boundary scripts are parser-inserted into the initial HTML without a nonce and are blocked by CSP strict-dynamic.

1. Clone https://github.com/Vatroslav/next-csp-nonce-repro. 2. Run `npm install && npm run build && npm start`. 3. Open http://localhost:3000/repro in a browser with the console open, using a full page load (hard reload or directly typing the URL). 4. Observe the CSP violation in the console, or run `curl -s http://localhost:3000/repro | grep -o '<script[^>]*>' | grep -v nonce` to see the missing nonce attribute.

Fixing Code Block

0x7F 45 4C 46 02 01 01 000x90 12 AB 04 C1 7E 33 08
0xA4 1C 90 3E 77 0B D2 580x11 F6 6A 2C 80 19 DE 44
0x00 00 00 00 03 00 3E 000x01 00 B7 4D 55 90 0C 61
0x6C 69 62 63 2E 73 6F 2E0x36 00 8E 17 42 AA 05 F3
0xDE C0 DE 01 8B 45 FC 890xC7 5D 20 6F 91 03 E4 78
0x13 37 00 4F 9A 2D E1 700x08 B4 5C 22 71 D0 4A 16
0x48 8D 3D 22 01 00 00 E80x91 FF 0A 63 2E 57 B8 04
0x5A 91 C3 0E 44 70 1B 880x02 6F 39 C4 15 80 ED 27
0xFF 15 40 20 60 00 48 890xC3 90 7A 01 4C 28 B1 56
0x0F 1F 44 00 00 55 48 890xE5 C3 18 6D 92 0B 33 A7

Edge Case Audit

This change may expose the nonce in the HTML only where it is already intended; no new risky exposure is introduced. However, if the application uses a nonce that changes between requests (recommended), any cached HTML or CDN-cached pages that include the old nonce will continue to be blocked until cache invalidation. To roll back, simply remove the `nonce: ctx.nonce` line from the script props. No other code depends on this prop.