@conform-to/dom parseSubmission vulnerable to CPU exhaustion when parsing many unique form fields

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-49250: 0.51% estimated exploitation activity in the next 30 days; percentile 43.84 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A CPU exhaustion vulnerability exists in Conform's 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 provides maxParts, maxTotalSize, maxFileSize, maxFiles, and maxHeaderSize options.

Published by the source

2 Jul 2026, 19:18 UTC

Last modified by the source

10 Sep 2026, 03:51 UTC

Source last checked

26 Oct 2026, 12:56 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-525m-7f82-2mf7

2. Revision 2 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-525m-7f82-2mf7

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-49250

Advisory: @conform-to/dom parseSubmission vulnerable to CPU exhaustion when parsing many unique form fields
IDs: CVE-2026-49250, GHSA-525m-7f82-2mf7
Record: https://patchnext.com/advisories/cve-2026-49250 (revision 3, source checked 26 Oct 2026, 12:56 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @conform-to/dom 1.19.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @conform-to/dom: affected >= 1.8.0, < 1.19.4; fixed in 1.19.4

## Suggested inspection (read-only)
- `npm ls @conform-to/dom --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @conform-to/dom.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-525m-7f82-2mf7 (OSV record GHSA-525m-7f82-2mf7 lists affected ranges: npm @conform-to/dom >=1.8.0 <1.19.4 (fixed))
- Verified: https://github.com/advisories/GHSA-525m-7f82-2mf7 (GitHub-reviewed advisory GHSA-525m-7f82-2mf7 lists affected ranges: npm @conform-to/dom >=1.8.0 <1.19.4)

Commands are suggestions: review each one before running it.