Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-24888: CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in microsoft maker.js

0
Medium
VulnerabilityCVE-2026-24888cvecve-2026-24888cwe-1321
Published: Wed Jan 28 2026 (01/28/2026, 21:35:44 UTC)
Source: CVE Database V5
Vendor/Project: microsoft
Product: maker.js

Description

CVE-2026-24888 is a medium severity prototype pollution vulnerability in Microsoft maker. js versions up to 0. 19. 1. The issue arises from the makerjs. extendObject function, which copies properties from source objects to target objects without proper validation such as hasOwnProperty checks. This allows attackers to inject or modify inherited prototype properties, potentially leading to data manipulation or logic errors in applications using maker. js for 2D vector drawing and CNC/laser cutting modeling. Exploitation does not require authentication or user interaction and can be performed remotely. A patch fixing this issue is included in version 0.

AI-Powered Analysis

AILast updated: 02/05/2026, 08:54:49 UTC

Technical Analysis

Microsoft maker.js is a JavaScript library used for 2D vector line drawing and shape modeling, particularly in CNC and laser cutting applications. Versions up to and including 0.19.1 contain a prototype pollution vulnerability identified as CVE-2026-24888 (CWE-1321). The root cause is the makerjs.extendObject function, which merges properties from source objects into target objects without verifying if those properties are own properties of the source object. Specifically, the function lacks hasOwnProperty() checks and does not filter out dangerous keys, enabling attackers to inject or modify prototype attributes. This improper handling allows malicious actors to manipulate the prototype chain, potentially altering application behavior, bypassing security controls, or corrupting data structures. The vulnerability can be exploited remotely without authentication or user interaction, increasing the attack surface. Although no known exploits have been reported in the wild, the issue poses a tangible risk to applications relying on maker.js for critical manufacturing or design processes. A patch addressing this vulnerability has been committed (commit 85e0f12bd868974b891601a141974f929dec36b8) and is expected in version 0.19.2. The CVSS 3.1 base score is 6.5, reflecting a medium severity level due to the potential impact on confidentiality and integrity but no impact on availability.

Potential Impact

For European organizations, especially those in manufacturing, industrial design, and CNC/laser cutting sectors, this vulnerability could lead to unauthorized modification of design data or application logic, potentially causing defective product outputs or intellectual property exposure. The integrity of design files and manufacturing instructions could be compromised, leading to financial losses, production delays, or safety hazards if maliciously altered. Confidential information embedded in design metadata might also be exposed or manipulated. Since maker.js is a specialized library, the impact is concentrated on organizations integrating it into their design or manufacturing pipelines. Disruption or manipulation of these processes could have downstream effects on supply chains and product quality. Given the remote exploitability without authentication, attackers could target vulnerable systems over the internet or internal networks, increasing risk for organizations with exposed development or manufacturing environments.

Mitigation Recommendations

European organizations using maker.js should immediately upgrade to version 0.19.2 or later, which includes the patch for this vulnerability. If upgrading is not immediately feasible, implement strict input validation and sanitization on any data passed to makerjs.extendObject to prevent malicious prototype properties from being introduced. Employ runtime security controls such as JavaScript sandboxing or object freezing to limit prototype chain modifications. Conduct thorough code reviews and dependency audits to identify and remediate usage of vulnerable versions. Additionally, restrict network access to development and manufacturing systems using maker.js to trusted users and networks only. Monitor logs for unusual object property manipulations or errors indicative of prototype pollution attempts. Finally, educate developers on secure coding practices related to object property handling to prevent similar issues.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-01-27T19:35:20.528Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 697a84c24623b1157cf1f0bb

Added to database: 1/28/2026, 9:50:58 PM

Last enriched: 2/5/2026, 8:54:49 AM

Last updated: 2/7/2026, 12:48:37 AM

Views: 50

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats