Dottie provides nested object access and manipulation in JavaScript. Versions 2.0.4 through 2.0.6 contain an incomplete fix for CVE-2023-26132. The prototype pollution guard introduced in commit `7d3aee1` only validates the first segment of a dot-separated path, allowing an attacker to bypass the protection by placing `__proto__` at any position other than the first. Both `dottie.set()` and `dottie.transform()` are affected. Version 2.0.7 contains an updated fix to address the residual vulnerability.
Swiper is a free and mobile touch slider with hardware accelerated transitions and native behavior. Versions 6.5.1 through 12.1.1 have a Prototype pollution vulnerability. The vulnerability resides in line 94 of shared/utils.mjs, where the indexOf() function is used to check whether user provided input contain forbidden strings. Despite a previous fix that attempted to mitigate prototype pollution by checking whether user input contained a forbidden key, it is still possible to pollute Object.prototype via a crafted input using Array.prototype. The exploit works across Windows and Linux and on Node and Bun runtimes. Any application that processes attacker-controlled input using this package may be affected by the following: Authentication Bypass, Denial of Service and RCE. This issue is fixed in version 12.1.2.
set-in provides the set value of nested associative structure given array of keys. A prototype pollution vulnerability exists in the the npm package set-in (>=2.0.1, < 2.0.5). Despite a previous fix that attempted to mitigate prototype pollution by checking whether user input contained a forbidden key, it is still possible to pollute Object.prototype via a crafted input using Array.prototype. This has been fixed in version 2.0.5.
CVE-2026-25881 is a critical prototype pollution vulnerability in SandboxJS versions prior to 0.8.31. It allows sandboxed JavaScript code to escape isolation by mutating host built-in prototypes such as Map.prototype or Set.prototype. This occurs because the isGlobal protection flag is improperly stripped when global prototype references are passed through array literals, enabling persistent prototype pollution. Exploiting this flaw can lead to remote code execution (RCE) if polluted properties are used in sensitive operations like execSync. The vulnerability has a CVSS score of 9.1, indicating high severity, and affects applications relying on SandboxJS for secure code execution.
AdonisJS is a TypeScript-first web framework. Prior to versions 10.1.3 and 11.0.0-next.9, a prototype pollution vulnerability in AdonisJS multipart form-data parsing may allow a remote attacker to manipulate object prototypes at runtime. This issue has been patched in versions 10.1.3 and 11.0.0-next.9.
Locutus brings stdlibs of other programming languages to JavaScript for educational purposes. In versions from 2.0.12 to before 2.0.39, a prototype pollution vulnerability exists in locutus. Despite a previous fix that attempted to mitigate prototype pollution by checking whether user input contained a forbidden key, it is still possible to pollute Object.prototype via a crafted input using String.prototype. This issue has been patched in version 2.0.39.
CVE-2026-25150 is a critical prototype pollution vulnerability in the QwikDev qwik JavaScript framework versions prior to 1.19.0. The flaw exists in the formToObj() function of the @builder.io/qwik-city middleware, which improperly processes form field names containing dot notation without sanitizing dangerous property names like __proto__, constructor, and prototype. This allows unauthenticated attackers to send crafted HTTP POST requests that modify Object.prototype, potentially leading to privilege escalation, authentication bypass, or denial of service. The vulnerability has a CVSS score of 9.3, indicating critical severity, and affects all deployments using vulnerable qwik versions. Although no known exploits are currently in the wild, the ease of exploitation and impact on integrity make this a high-risk issue.
deepHas provides a test for the existence of a nested object key and optionally returns that key. A prototype pollution vulnerability exists in version 1.0.7 of the deephas npm package that allows an attacker to modify global object behavior. This issue was fixed in version 1.0.8.
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.
CVE-2026-23736 is a high-severity prototype pollution vulnerability in the seroval JavaScript value stringification library (versions below 1.4.1). The flaw arises from improper input validation during JSON deserialization, allowing attackers to modify object prototype attributes maliciously. Exploitation requires no authentication or user interaction and can be performed remotely over the network. Successful attacks can lead to partial compromise of confidentiality, integrity, and availability of affected applications. The vulnerability is fixed in seroval version 1.4.1. European organizations using vulnerable versions in their JavaScript environments should prioritize updating to mitigate risks.
The Tarkov Data Manager is a tool to manage the Tarkov item data. Prior to 02 January 2025, an authentication bypass vulnerability in the login endpoint allows any unauthenticated user to gain full admin access to the Tarkov Data Manager admin panel by exploiting a JavaScript prototype property access vulnerability, combined with loose equality type coercion. A series of fix commits on 02 January 2025 fixed this and other vulnerabilities.
Prototype pollution vulnerability in apidoc-core versions 0.2.0 and all subsequent versions allows remote attackers to modify JavaScript object prototypes via malformed data structures, including the “define” property processed by the application, potentially leading to denial of service or unintended behavior in applications relying on the integrity of prototype chains. This affects the preProcess() function in api_group.js, api_param_title.js, api_use.js, and api_permission.js worker modules.
CVE-2025-8083 is a high-severity prototype pollution vulnerability in Vuetify versions 2.2.0-beta.2 up to but not including 3.0.0-alpha.10. It arises from the 'mergeDeep' utility used in the Preset configuration feature, allowing attackers to inject arbitrary properties into all JavaScript objects. This can lead to denial of service, unauthorized data access, and unpredictable application behavior. The vulnerability is especially critical for applications using Server-Side Rendering (SSR), as it can compromise the entire server process.
CVE-2025-66456 is a critical prototype pollution vulnerability in the Elysia Typescript framework versions 1.4.0 through 1.4.16. It arises from improper merging of schema validation results in the mergeDeep function, allowing an attacker to manipulate the __proto__ property. When combined with another vulnerability (GHSA-8vch-m3f4-q8jf), this can lead to full remote code execution (RCE) without authentication or user interaction. The vulnerability has a CVSS 4.0 score of 9.1, indicating high severity.
npm package `expr-eval` is vulnerable to Prototype Pollution. An attacker with access to express eval interface can use JavaScript prototype-based inheritance model to achieve arbitrary code execution. The npm expr-eval-fork package resolves this issue.
js-yaml is a JavaScript YAML parser and dumper. In js-yaml before 4.1.1 and 3.14.2, it's possible for an attacker to modify the prototype of the result of a parsed yaml document via prototype pollution (`__proto__`). All users who parse untrusted yaml documents may be impacted. The problem is patched in js-yaml 4.1.1 and 3.14.2. Users can protect against this kind of attack on the server by using `node --disable-proto=delete` or `deno` (in Deno, pollution protection is on by default).
The expr-eval library is a JavaScript expression parser and evaluator designed to safely evaluate mathematical expressions with user-defined variables. However, due to insufficient input validation, an attacker can pass a crafted context object or use MEMBER of the context object into the evaluate() function and trigger arbitrary code execution.
Rollbar.js offers error tracking and logging from Javascript to Rollbar. In versions before 2.26.5 and from 3.0.0-alpha1 to before 3.0.0-beta5, there is a prototype pollution vulnerability in merge(). If application code calls rollbar.configure() with untrusted input, prototype pollution is possible. This issue has been fixed in versions 2.26.5 and 3.0.0-beta5. A workaround involves ensuring that values passed to rollbar.configure() do not contain untrusted input.
In versions before 20.0.2, it was found that --disallow-code-generation-from-strings is not sufficient for isolating untrusted JavaScript in happy-dom. The untrusted script and the rest of the application still run in the same Isolate/process, so attackers can deploy prototype pollution payloads to hijack important references like "process" in the example below, or to hijack control flow via flipping checks of undefined property. This vulnerability is due to an incomplete fix for CVE-2025-61927. The vulnerability is fixed in 20.0.2.
sveltekit-superforms makes SvelteKit forms a pleasure to use.sveltekit-superforms v2.27.3 and prior are susceptible to a prototype pollution vulnerability within the parseFormData function of formData.js. An attacker can inject string and array properties into Object.prototype, leading to denial of service, type confusion, and potential remote code execution in downstream applications that rely on polluted objects. This vulnerability is fixed in 2.27.4.