dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2024-57068

HIGH · 7.5 CVSS v3.1 Published 2025-02-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A prototype pollution in the lib.mutateMergeDeep function of @tanstack/form-core v0.35.0 allows attackers to cause a Denial of Service (DoS) via supplying a crafted payload.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A prototype pollution vulnerability exists in the lib.mutateMergeDeep function of @tanstack/form-core v0.35.0. Attackers can exploit this by supplying a crafted payload that modifies the JavaScript object's prototype chain, leading to denial of service.

MitigationUpgrade @tanstack/form-core to the latest patched version. Review all usage of mutateMergeDeep function and validate input data to prevent prototype pollution vectors.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check @tanstack/form-core version
    Run 'npm list @tanstack/form-core' or check package.json dependencies to identify the installed version
    Affected if Installed version is v0.35.0 or any version prior to the patched release
  2. Locate mutateMergeDeep usage
    Search codebase for imports or references to 'mutateMergeDeep' from '@tanstack/form-core' (e.g., grep for 'mutateMergeDeep' or 'lib.mutateMergeDeep')
    Affected if The mutateMergeDeep function from @tanstack/form-core is imported and used in the codebase
  3. Inspect input sources to mutateMergeDeep
    Review all call sites where mutateMergeDeep is invoked and trace the origin of arguments passed to it
    Affected if Untrusted or user-controlled data is passed as an argument to mutateMergeDeep without sanitization

You are affected if @tanstack/form-core v0.35.0 (or an unpatched version) is installed AND the mutateMergeDeep function is being called with untrusted input, allowing prototype pollution vectors.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade @tanstack/form-core to the latest patched version. Review all usage of mutateMergeDeep function and validate input data to prevent prototype pollution vectors.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-57068 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-57068 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data