CVE-2026-46510: kaspernj form-data-objectizer · Prototype Pollution
Affects kaspernj form-data-objectizerSource CVE Database V5
Not known to be exploited · CVSS 8.2 High : upgrade to 1.0.1 soon.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.0.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 29 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade kaspernj form-data-objectizer to 1.0.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| kaspernjform-data-objectizer | Affected
| Fixed in
|
npmform-data-objectizerpkg:npm/form-data-objectizerOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade the kaspernj form-data-objectizer library to version 1.0.1 or later, where this prototype pollution vulnerability is fixed. Avoid using vulnerable versions (<1.0.1) in production environments. Patch status is not explicitly confirmed beyond the version fix, so check the vendor advisory for the latest remediation guidance.
Description
form-data-objectizer converts FormData to object. Prior to 1.0.1, form-data-objectizer walks bracket-notation form keys (e.g.name[sub]) into nested objects without filtering __proto__, constructor, or prototype. A single HTTP form field whose name starts with __proto__[...] causes the library to mutate Object.prototype, which is a prototype pollution primitive of the entire Node.js process. This vulnerability is fixed in 1.0.1.