Loading...
Skip to main content

CVE-2024-32866 — Vulnerability in @conform-to/zod — CVE Details

HIGH

Conform contains a Prototype Pollution Vulnerability in `parseWith...` function

Published April 23, 2024Updated September 10, 2026Source: osv

Summary

### Summary Conform allows the parsing of nested objects in the form of `object.property`. Due to an improper implementation of this feature, an attacker can exploit it to trigger prototype pollution by passing a crafted input to `parseWith...` functions. ### PoC ```javascript const { parseWithZod } = require('@conform-to/zod'); const { z } = require("zod"); const param = new URLSearchParams("__proto__.pollution=polluted"); const schema = z.object({ "a": z.string() }); parseWithZod(param, { schema }); console.log("pollution:", ({}).pollution); // should print "polluted" ``` ### Details The invocation of the `parseWithZod` function in the above PoC triggers the `setValue` function through `getSubmissionContext` and `parse`, executing the following process, resulting in prototype pollution: ```javascript let pointer = value; pointer.__proto__ = pointer.__proto__; pointer = pointer.__proto__; pointer.polluted = "polluted"; ``` This is caused by the lack of object existence checking on [line 117 in formdata.ts](https://github.com/edmundhung/conform/blob/59156d7115a7207fa3b6f8a70a4342a9b24c2501/packages/conform-dom/formdata.ts#L117), where the code only checks for the presence of `pointer[key]` without proper validation. ### Impact Applications that use conform for server-side validation of form data or URL parameters are affected by this vulnerability.

Advisory Timeline

  • First published April 23, 2024 (902 days ago).
  • Last revised September 10, 2026 — 869 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

npm
Update @conform-to/zod to 0.9.2 or later
npm install @conform-to/zod@0.9.2
npm
Update @conform-to/dom to 0.9.2 or later
npm install @conform-to/dom@0.9.2
npm
Update @conform-to/dom to 1.1.1 or later
npm install @conform-to/dom@1.1.1
npm
Update @conform-to/yup to 0.9.2 or later
npm install @conform-to/yup@0.9.2
npm
Update @conform-to/zod to 1.1.1 or later
npm install @conform-to/zod@1.1.1
npm
Update @conform-to/yup to 1.1.1 or later
npm install @conform-to/yup@1.1.1

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (6)

Affects 1 ecosystem: npm (3).

PackageEcosystemAffectedFixed In
@conform-to/zod
npm
All versions0.9.2
@conform-to/dom
npm
All versions0.9.2
@conform-to/dom
npm
All versions1.1.1
@conform-to/yup
npm
All versions0.9.2
@conform-to/zod
npm
All versions1.1.1
@conform-to/yup
npm
All versions1.1.1

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

  • CWE-1321
    Prototype PollutionMITRE

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 8.6 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H

Frequently Asked Questions

What is CVE-2024-32866?
Conform contains a Prototype Pollution Vulnerability in `parseWith...` function This vulnerability has been assigned a severity rating of HIGH (CVSS score: 8.6/10).
How do I check if my project is affected by CVE-2024-32866?
CVE-2024-32866 affects @conform-to/zod, @conform-to/dom and @conform-to/yup. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2024-32866 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
8.6

High exploitability or significant impact. Prioritize remediation within days.

Also Known As

GHSA-624g-8qjg-8qxf

Related CVEs

  • CVE-2026-107375
    HIGH

    JHipster: SQL Injection in the Parameter of JHipster-Generated Reactive (WebFlux + R2DBC) Applicationssort

  • CVE-2026-107384
    HIGH

    MariaDB Connector/Node.js: SQL injection through object keys in SET expansion (permitSetMultiParamEntries)

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies