Skip to main content
HighCodeCWE-1321

How to fix: Custom recursive merge prototype pollution

Hand-rolled recursive merge functions that iterate Object.keys(source) and recurse into nested values will write through __proto__ and pollute Object.prototype when the source is attacker-controlled.

Why it matters

Same downstream impact as library-driven prototype pollution: XSS, auth bypass, DoS.

The `code-proto-pollution-recursive-merge` check verifies that the server does not expose the `proto-pollution-recursive-merge` weakness in the code category. The detection runs against the response headers, body, or auxiliary probes (DNS, TLS, async fetch) as appropriate.

How to fix it

  1. 1Skip keys named __proto__, constructor, or prototype in the merge loop.
  2. 2Use Object.hasOwn(target, key) to guard against inherited keys.
  3. 3Replace the custom helper with a vetted library patched against pollution.

Code examples

Freeze Object.prototype in tests to catch pollution

TypeScript
// In tests, freeze Object.prototype to catch pollution
beforeEach(() => Object.freeze(Object.prototype));
afterEach(() => Object.isFrozen(Object.prototype) && /* nothing to restore */ null);

// In production code: use Object.create(null) for user-data maps
const userMap = Object.create(null); // no prototype chain

References

Detected automatically by VulnRadar. The check id is code-proto-pollution-recursive-merge, stable across every scan so you can filter or diff on it.

See every code check

Questions

How severe is Custom recursive merge prototype pollution?
VulnRadar rates this high 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 code-proto-pollution-recursive-merge, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Custom recursive merge prototype pollution map to?
It maps to CWE-1321.

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 custom recursive merge prototype pollution

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

Custom recursive merge prototype pollution fix | VulnRadar