{"answers":{"affected":"2 open source packages ship an affected version, including @conform-to/dom.","exploited":"There is no known exploitation of CVE-2026-49250 in the wild and no public exploit code.","fix":"Upgrade @conform-to/dom to 1.19.4 or later.","what":"CVE-2026-49250 is a high-severity denial of service vulnerability in edmundhung conform, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-49250 and fix it if it is affected.\n\nWhat it is: CVE-2026-49250 is a high-severity denial of service vulnerability in edmundhung conform, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-49250 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @conform-to/dom (npm): affected from 1.8.0; fixed in 1.19.4\n- @conform-to/dom (npm): affected from 1.8.0; fixed in 1.19.4\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-49250/ (Markdown: https://insights.sbomify.com/CVE-2026-49250/index.md)","id":"CVE-2026-49250","markdown":"https://insights.sbomify.com/CVE-2026-49250/index.md","name":"CVE-2026-49250","record":{"aliases":["GHSA-525m-7f82-2mf7"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript form validation library","requires_auth":"none","summary":"An unauthenticated attacker can cause CPU exhaustion and denial of service by submitting a form with many unique field names to applications using the Conform library.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-407","name":"Inefficient Algorithmic Complexity"}],"description":"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Conform: parseSubmission vulnerable to CPU exhaustion when parsing many unique form fields","id":"CVE-2026-49250","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"deepstream is vulnerable to prototype pollution","id":"CVE-2026-49252"},"packages":[{"ecosystem":"npm","fixed":["1.19.4"],"introduced":["1.8.0"],"last_affected":[],"package":"@conform-to/dom","purl":null,"source":"GHSA-525m-7f82-2mf7"},{"ecosystem":"npm","fixed":["1.19.4"],"introduced":["1.8.0"],"last_affected":[],"package":"@conform-to/dom","purl":"pkg:npm/%40conform-to/dom","source":"GHSA-525m-7f82-2mf7"}],"prev":{"headline":"Boruta: Authenticated atom-exhaustion DoS in BorutaIdentityWeb.UserSettingsController.update/2","id":"CVE-2026-49249"},"products":["conform"],"published":"2026-09-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-14","vendors":["edmundhung"]},"summary":"An unauthenticated attacker can cause CPU exhaustion and denial of service by submitting a form with many unique field names to applications using the Conform library.","url":"https://insights.sbomify.com/CVE-2026-49250/"}