CVE-2026-49250

HIGHPre-NVD 8.78.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.7
EG Score
8.7(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity87% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

July 2, 2026

Last Modified

September 14, 2026

Advisory Details (3)

Auto-updated Sep 14, 2026
Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

v1.19.4

Patch available: edmundhung/conform v1.19.4

https://github.com/edmundhung/conform/releases/tag/v1.19.4
github_commit Patch Available

commit f9a1e696ef95 (edmundhung/conform)

Patch available: edmundhung/conform v1.19.4 (contains commit f9a1e696ef95)

https://github.com/edmundhung/conform/commit/f9a1e696ef950efcada5f06ea2b202da505bf9b0
github Patch Available

parseSubmission vulnerable to CPU exhaustion when parsing many unique form fields · Advisory · edmundhung/conform · GitHub

https://github.com/edmundhung/conform/security/advisories/GHSA-525m-7f82-2mf7

Vendor Advisories for CVE-2026-49250(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
@conform-to/dom—1.19.4—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 06:15 UTCEG score recompute
  3. 2026-09-16 14:08 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-14 18:38 UTCEG score recompute
  6. 2026-09-14 17:21 UTCEG score recompute▲ 8.70
  7. 2026-09-14 17:21 UTCMITRE cvelistV5CVSS v3 → 8.7 · CVSS v4 → 8.7
  8. 2026-08-01 02:07 UTCEG score recompute
  9. 2026-07-26 13:04 UTCEG score recompute
  10. 2026-07-23 03:18 UTCEG score recompute
  11. 2026-07-02 20:07 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-49250?
CVE-2026-49250 is a high vulnerability published on July 2, 2026. 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…
When was CVE-2026-49250 disclosed?
CVE-2026-49250 was first published in the National Vulnerability Database on July 2, 2026, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49250 actively exploited?
CVE-2026-49250 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 77.6% of all scored CVEs.
What is the CVSS score of CVE-2026-49250?
CVE-2026-49250 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-49250?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49250, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49250

Explore →

Is Your Infrastructure Affected by CVE-2026-49250?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs