InfoCode
How to fix: WebAssembly Usage Detected
WebAssembly modules detected.
Why it matters
WASM code harder to audit.
WebAssembly runs compiled code in browser.
How to fix it
- 1Ensure WASM source is trusted.
Code examples
Validate WASM origin and use CSP wasm-unsafe-eval policy
// Only load WASM from your own origin
const response = await fetch("/wasm/module.wasm");
const { instance } = await WebAssembly.instantiateStreaming(response);
// CSP: add wasm-unsafe-eval only if required by the module
// Never load WASM from user-supplied URLsReferences
Detected automatically by VulnRadar. The check id is wasm-usage, stable across every scan so you can filter or diff on it.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- MediumPotential Prototype Pollution Sinks Detected
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
Questions
- How severe is WebAssembly Usage Detected?
- VulnRadar rates this info severity in the code 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 wasm-usage, 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.