CVE-2024-57079
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 · uneditedA prototype pollution in the lib.deepMerge function of @zag-js/core v0.50.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 confidenceA prototype pollution vulnerability exists in the lib.deepMerge function of @zag-js/core v0.50.0. Attackers can supply a crafted payload that pollutes the JavaScript prototype object, which can lead to denial of service by causing unexpected behavior or application crashes.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed version of @zag-js/coreRun 'npm list @zag-js/core' or check package.json dependencies to see the exact version installedAffected if The installed version is v0.50.0 specifically (the only affected version listed in this CVE)
-
Locate deepMerge usage in codebaseSearch for imports or references to 'deepMerge' from '@zag-js/core' or 'lib.deepMerge' in your source code using grep or IDE searchAffected if Your codebase imports and uses the deepMerge function from @zag-js/core
-
Inspect input sources to deepMergeTrace all call sites of deepMerge and identify whether any receive data from external sources (HTTP requests, user input, APIs, JSON parsing)Affected if Untrusted or user-supplied data is passed as an argument to deepMerge without prior sanitization
-
Check for prototype-manipulating properties in input handlingReview the data flow into deepMerge calls and look for objects containing '__proto__', 'constructor', or 'prototype' keys that could be mergedAffected if Input passed to deepMerge may contain object keys that could modify the JavaScript prototype object
You are affected if @zag-js/core v0.50.0 is installed and untrusted input reaches the deepMerge function without validation.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedUpdate to a patched version of @zag-js/core when available. Until then, validate and sanitize all input passed to the deepMerge function to reject prototype-manipulating payloads.
latest stable version of @zag-js/core (version >0.50.0)
- Update the @zag-js/core dependency in package.json to a version greater than 0.50.0 (e.g., use ^0.51.0 or @latest).
- Run npm install or yarn install to fetch the updated package.
- Test the application to confirm the prototype pollution issue in lib.deepMerge is resolved.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-57079 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-57079 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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