Skip to main content

How to fix: CSP Header > 4KB

CSP headers longer than ~4KB are silently dropped by some browsers.

Why it matters

Split into multiple CSPs via report-to, or use nonces instead of inline source lists

CSP headers longer than ~4KB are silently dropped by some browsers.

How to fix it

  1. 1Split into multiple CSPs via report-to, or use nonces instead of inline source lists

Code examples

Simplify CSP using strict-dynamic and nonces

TypeScript
// A CSP with hundreds of allowlisted URLs is unmaintainable and often too permissive
// Use nonce + strict-dynamic instead:
import { randomBytes } from "crypto";
const nonce = randomBytes(16).toString("base64");

// CSP becomes short and strict:
// script-src 'nonce-{nonce}' 'strict-dynamic'; object-src 'none'; base-uri 'none';
// strict-dynamic allows scripts loaded by trusted nonce'd scripts automatically

References

Detected automatically by VulnRadar. The check id is csp-too-long, stable across every scan so you can filter or diff on it.

See every headers check

Questions

How severe is CSP Header > 4KB?
VulnRadar rates this low severity in the headers category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id csp-too-long, which stays the same between runs so you can filter, diff, or gate CI on it.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for csp header > 4kb

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: CSP Header > 4KB | VulnRadar