A CPU exhaustion vulnerability exists in Conform's [parseSubmission](https://conform.guide/api/react/future/parseSubmission) future API when parsing FormData or URLSearchParams submissions with many unique field names.…
| CVE ID | CVE-2026-49250 |
| Vendor | npm |
| Affected Product | @conform-to/dom |
| Vulnerability Type | Vulnerability |
| CVSS Score | 7.5 (HIGH) |
| Actively Exploited | ❌ No known exploitation |
| Patch Status | See Vendor Advisory → |
| Reported By | CYBERDUDEBIVASH SENTINEL APEX Intelligence (via github_advisories) |
A CPU exhaustion vulnerability exists in Conform's [parseSubmission](https://conform.guide/api/react/future/parseSubmission) future API when parsing FormData or URLSearchParams submissions with many unique field names. The parser previously looked up values by field name, which could require repeated scans of the submitted entries and cause excessive synchronous CPU work if an attacker supplies a crafted submission. > [!NOTE] > The patched version fixes this by iterating submitted entries directly instead of repeatedly looking up values by field name. Applications that accept untrusted form submissions should still enforce request parsing limits before passing data to Conform. For multipart requests, [@remix-run/form-data-parser](https://www.npmjs.com/package/@remix-run/form-data-par
Sigma rules, YARA signatures, IOC table, and SIEM queries for Splunk, Elastic, Sentinel, and Chronicle — deployable in 5 minutes.