# CVE-2026-24888: Maker.js Vulnerable to Unsafe Property Copying in makerjs.extendObject


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 28 Jan 2026
- **Updated:** 29 Jan 2026
- **Also known as:** GHSA-2cp6-34r9-54xx

## What is CVE-2026-24888?

CVE-2026-24888 is a medium-severity vulnerability in microsoft maker.js, published on 28 Jan 2026. 

### Official description

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.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

## Which versions are affected by CVE-2026-24888?

2 open source packages ship an affected version, including makerjs. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `makerjs` | npm | All versions | 0.19.2 |
| `makerjs` | npm | All versions | 0.19.2 |

Products: Microsoft Maker.js.

## How do I fix CVE-2026-24888?

Upgrade makerjs to 0.19.2 or later.

## Is CVE-2026-24888 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24888 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24888 and fix it if it is affected.

What it is: CVE-2026-24888 is a medium-severity vulnerability in microsoft maker.js, published on 28 Jan 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24888 exists.

Affected packages and fixed versions:
- makerjs (npm): affected all versions; fixed in 0.19.2
- makerjs (npm): affected all versions; fixed in 0.19.2

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-24888/ (Markdown: https://insights.sbomify.com/CVE-2026-24888/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24888
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24888
- OSV: https://osv.dev/vulnerability/CVE-2026-24888

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-24888/
Summaries are generated and may contain mistakes; the official description above is the record.