cve.bz

CVE-2026-49250 edmundhung conform: Inefficient Algorithmic Complexity

8.7 highEPSS 0.5%Fix available

High (8.7) in edmundhung conform. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in @conform-to/dom 1.19.4.

On this page
Conform, a type-safe form validation library, allows the parsing of nested objects in the form of object.property. From 1.8.0 until 1.19.4, the parseSubmission future API in packages/conform-dom/formdata.ts repeatedly scans FormData or URLSearchParams entries by each unique field name. An unauthenticated attacker can submit a crafted form containing many unique names, causing excessive synchronous CPU work and denial of service in an application that passes the submission to parseSubmission. Applications should continue to enforce request parsing limits before invoking Conform. This issue is fixed in version 1.19.4.

Severity

CVSS 4.0

8.7 high
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
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 44th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-09-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-407 Inefficient Algorithmic Complexity
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • @conform-to/dom (npm): fixed in 1.19.4

Ask an AI about this CVE

Show the promptExplain CVE-2026-49250 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-49250?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-49250?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-49250 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
edmundhung conform>= 1.8.0, < 1.19.4

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-525m-7f82-2mf7npm@conform-to/dom>=1.8.0 <1.19.41.19.4

References

Check your stackJSON