How to fix: Script from blob: URL
Script loaded from blob: URL.
Why it matters
Dynamic script generation.
Blob URLs can be used to execute dynamic scripts.
How to fix it
- 1Consider blocking blob: in CSP.
Code examples
Restrict blob: URL script execution via CSP
// CSP: restrict blob: in script-src
res.setHeader("Content-Security-Policy",
"script-src 'self'; worker-src 'self' blob:; object-src 'none';"
);
// worker-src blob: is needed for Web Workers but limits blob URL scripts
// Never create blob: URLs from user content for script executionReferences
Detected automatically by VulnRadar. The check id is blob-url-script, stable across every scan so you can filter or diff on it.
More content checks
- MediumPotential Open Redirect Parameters
- HighDirectory Listing Appears Enabled
- MediumSensitive File References Detected
- HighPotentially Outdated JavaScript Libraries
- Inforobots.txt Present - Review Manually
- InfoCMS / Technology Fingerprinting
- MediumPotentially Dangerous Inline JavaScript
- LowServer version disclosed in response header
Questions
- How severe is Script from blob: URL?
- VulnRadar rates this medium severity in the content 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 blob-url-script, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Script from blob: URL map to?
- It maps to CWE-79. In the OWASP Top 10 it falls under A03:2021.
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.