dbcve.org
Maker.jsApplication · Microsoft

CVE-2026-24888

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-28
Fix available
A fix is available. Upgrade to after 0.19.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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
Maker.js is a 2D vector line drawing and shape modeling for CNC and laser cutters. In versions up to and including 0.19.1, the `makerjs.extendObject` function copies properties from source objects without proper validation, potentially exposing applications to security risks. The function lacks `hasOwnProperty()` checks and does not filter dangerous keys, allowing inherited properties and potentially malicious properties to be copied to target objects. A patch is available in commit 85e0f12bd868974b891601a141974f929dec36b8, which is expected to be part of version 0.19.2.

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 · high confidence

Maker.js versions up to 0.19.1 contain a prototype pollution vulnerability in the `makerjs.extendObject` function. The function copies properties from source objects to target objects without using `hasOwnProperty()` checks or filtering dangerous keys, allowing attackers to inject malicious inherited properties (such as __proto__) into target objects.

MitigationUpgrade to Maker.js version 0.19.2 or later which includes the patch (commit 85e0f12) that adds proper hasOwnProperty validation and dangerous key filtering to the extendObject function.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Maker.jsApplication
Affected:<= 0.19.1

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Identify installed Maker.js version
    Check package.json, package-lock.json, or run `npm list makerjs` to see the installed version
    Affected if version is 0.19.1 or lower
  2. Locate the extendObject function in the codebase
    Search for usages of `makerjs.extendObject` or `extendObject` in your project code and dependencies
    Affected if the function is called with user-controlled objects as arguments
  3. Inspect the extendObject function implementation
    Examine the makerjs library file (typically in node_modules/makerjs) and locate the extendObject function definition
    Affected if the function lacks hasOwnProperty checks before copying properties (the vulnerable version <= 0.19.1)
  4. Verify prototype pollution is possible
    Pass an object containing __proto__ or constructor properties as the source argument to extendObject and inspect the target object after the call
    Affected if the dangerous keys are successfully merged into the target object

You are affected if Maker.js version is 0.19.1 or lower AND your code uses extendObject with untrusted input that could inject prototype properties.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 0.19.1
Vendor patch github.com →
Interim mitigation

Upgrade to Maker.js version 0.19.2 or later which includes the patch (commit 85e0f12) that adds proper hasOwnProperty validation and dangerous key filtering to the extendObject function.

Recommended fix High confidence

0.19.2

  1. Check the current version of maker.js in your project by running 'npm list makerjs' or reviewing your package.json file
  2. Upgrade maker.js to version 0.19.2 or later by running 'npm install [email protected]' or 'npm install makerjs@latest'
  3. After upgrading, run 'npm audit' to verify no known vulnerabilities remain
  4. Test your application thoroughly to ensure the fix does not break existing functionality that relies on the extendObject function
  5. If using a package-lock.json, consider deleting it and regenerating it with 'npm install' to ensure clean dependency resolution

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Maker.js Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24888 — 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-2026-24888 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